19 comments

[ 2.9 ms ] story [ 52.8 ms ] thread
POSIX
Heh. Especially true if we allow indirect to count, since I'll bet the vast majority of the web APIs upthread are hosted on *nix.
For https://MoonlightWork.com:

- Segment (backend event tracking and frontend management of things such as Google analytics)

- Intercom (frontend customer chat)

- Stripe (payments)

- Slack (we use the Api to correspond chat users with user accounts, and to create private channels for ongoing jobs)

- Sentry (error tracking with lots of additional information)

- Kubernetes (local and production application hosting setup)

- Contentful (CMS for our blog)

- Imgix (CDN that resizes photos on the fly - which we use for profile photos and logos)

We use a lot of the same stack. I particularly love imgix and stripe.
(comment deleted)
.net's System.Web and System.IO. Most of the code I write seems to use them somewhere. They're quite old, and not particularly well factored by modern standards, but I like their straightforwardness.
An internal API that I truly hate because of how poorly written it is. I’m probably going to rewrite it and quit.
(comment deleted)
Social Login APIs such as the FB api for apps I've published
For https://ably.io (Ably Realtime)

- Stripe (payments)

- PipeDrive & Intercom (CRM integration)

- Zapier (some automation between systems)

- Rollbar & Sentry (error tracking)

- AWS S3 (file storage)

- AWS Route53 & CloudFlare (DNS)

- AWS EC2 APIs (Infrastructure provisioning)

- AddSearch (search)

- Freshdesk (tickets)

- Sendgrid (email)

- Google Recaptha (captcha)

- APILayer (tax)

- Monitis & Uptrends (monitoring)

- Browserstack (browser automation)

We use 100s of services (https://blog.ably.io/94-tools-you-need-to-grow-your-startup-...), but I've only listed the key services where we integrate with their APIs.