This post is part of our Cloud Exit series. Over more than a decade we paid AWS about $244K, net of credits. Then we rebuilt on servers we own. Earlier posts cover the full cost story and how we swapped Lambda for cron. This one is about the database, and why moving it was the easy part.
Everything our 97 Lambda functions used to do now runs as a handful of Python scripts on a schedule, on servers we own. The SQS queues are gone and so are the SNS topics. When something breaks, there's one log file to read, not a chain of request IDs across five services. And the bill dropped fro...
Buzzwords worked. It read the news from dozens of sources, pulled out the words everyone was repeating, scored the mood of each channel, and told you what the world was talking about today. It started as one cloud function in August 2016 and grew into a real event-driven platform: 32 Lambda funct...
In 2019 we paid Amazon Web Services an average of about $4,500 a month. Today our infrastructure runs for about $100 a month, on hardware we own.
Our infrastructure now costs about $100 a month to run, on hardware we own. A few years ago, the same company was paying Amazon Web Services an average of about $4,500 a month. In 2025, with most of the move behind us, the cloud bill was still a few hundred dollars a month. Today the cloud is a s...
These cookies enable core functionality such as security, verification of identity and network management. These cookies can’t be disabled.
These cookies are used to track advertising effectiveness to provide a more relevant service and deliver better ads to suit your interests.
These cookies collect data to remember choices users make to improve and give a more personalised experience.
These cookies help us to understand how visitors interact with our website, discover errors and provide a better overall analytics.
