Checkly Inc.

Checkly Inc.

13 Followers
Delightful Active Monitoring for Developers
@checklyhq
checklyhq.com
Berlin, Utrecht, Boston
Tools by Checkly Inc.

Decisions 1

Tim Nolet

CTO at Checkly

When adding a new feature to Checkly rearchitecting some older piece, I tend to pick Heroku for rolling it out. But not always, because sometimes I pick AWS Lambda . The short story:

  • Developer Experience trumps everything.
  • AWS Lambda is cheap. Up to a limit though. This impact not only your wallet.
  • If you need geographic spread, AWS is lonely at the top.
The setup

Recently, I was doing a brainstorm at a startup here in Berlin on the future of their infrastructure. They were ready to move on from their initial, almost 100% Ec2 + Chef based setup. Everything was on the table. But we crossed out a lot quite quickly:

  • Pure, uncut, self hosted Kubernetes โ€” way too much complexity
  • Managed Kubernetes in various flavors โ€” still too much complexity
  • Zeit โ€” Maybe, but no Docker support
  • Elastic Beanstalk โ€” Maybe, bit old but does the job
  • Heroku
  • Lambda

It became clear a mix of PaaS and FaaS was the way to go. What a surprise! That is exactly what I use for Checkly! But when do you pick which model?

I chopped that question up into the following categories:

  • Developer Experience / DX ๐Ÿค“
  • Ops Experience / OX ๐Ÿ‚ (?)
  • Cost ๐Ÿ’ต
  • Lock in ๐Ÿ”

Read the full post linked below for all details

14 172.8K

Followers 13