“Learning-curve complexity is not equivalent to operating friction and complexity.” — Joe Emison
But it’s worth remembering the benefits you’re trading off this learning investment for. I wrote this article back in 2018 listing 30 (mostly operational) concerns that serverless obviates when compared to a server/container-based application. These are all still very relevant today and there are a few items I could add in (e.g. not having to rework slow SQL queries if using DynamoDB).
Some of these items may get dismissed as “later” concerns, but if you’re in the business of getting to production fast, then “later” could be within a month or two.
So while serverless still has some way to go to become more approachable for developers, once you’ve invested the time in learning, all these operational benefits are here for you today.
P.S. If you’re a startup or small team thinking about building a serverless app on AWS, I have some availability over next month to help you out (up to last week of June). How I can help:
- Serverless adoption considerations
- Architecture design workshop
- DevOps setup: AWS multi-acct org, CD pipelines
- Resolving issues in existing system or team delivery processes
- Ad-hoc dev team guidance
More details on my services here. Just reply to this email if you’re interested.
Indie Cloud Consultant helping small teams learn and build with serverless.
Learn more how I can help you here.
Join daily email list
I publish short emails like this on building software with serverless on a daily-ish basis. They’re casual, easy to digest, and sometimes thought-provoking. If daily is too much, you can also join my less frequent newsletter to get updates on new longer-form articles.