Member-only story

How To Refactor Serverless Applications the Right Way

And avoid losing momentum while doing it

Allen Helton
Better Programming
6 min readOct 22, 2021

--

People at construction site
Photo by Mark Potterton on Unsplash

Building modern apps is exciting. You get to learn new technology, converse with people in the industry that follow the same patterns, and explore new designs every day.

Imagine you are given the opportunity to build a greenfield application and you opt for tech decisions that have good industry backing and support, like serverless. You build your app over the course of months or years and when you go live, you’re done! Right?

Not even a little bit.

First of all, software is never done. You have invested in a time and energy black hole. There are new features and enhancements to build, defects to fix, and optimizations to be had.

You also have to take a step back, look at what you’ve done, and ask yourself “is this still relevant?”

If you took two years to build your production app (which is a totally acceptable time frame), chances are there have been a significant number of enhancements and new managed services released by your cloud vendor. Did you freeze your app at the moment in time when you started development?

Honestly, it’s easy to do. But what should you do when you find yourself in that situation? You could say you have a…

--

--

Allen Helton
Allen Helton

Written by Allen Helton

I am an AWS serverless hero with a strong focus on API design and standardization, event-driven architectures, and software automation.

No responses yet

What are your thoughts?