I'm running a recruitment platform for WoW guilds that has been online for more than a year. As with most side-projects, I knew my investment could change over time. So before starting, I tried envisioning what it would be like to maintain it six months later.
I realized that to make the project viable in the middle term, I needed to optimize money & time costs.
So the first goal was minimizing monthly fees, so that the project could live without any financial need for ‘success’. The second goal was to spend the most time shipping features—shorten the time from idea to production.
Luckily, I found one common solution to these two constraints, serverless applications.
The pricing formula for serverless is simple: you only pay for what you use. That's great, because if no uses your site, it costs you nothing. Plus, by freeing yourself from infrastructure management tasks, you also gain time to spend on things that matter.
Basically, less time worrying about infrastructure and more time developing features. :)
Serverless holds great promises. But building apps this way brings new constraints too. The back-end is now as a service and development requires a slight paradigm shift. Serverless architecture is most well complemented by the JAMstack.
With JAMstack, the website is just a front-end app. The backend is fully managed and available on-demand. To allow new features, we can plug in dedicated APIs. Adding unforeseen features will not require infrastructure changes.
The best part? These third-party services fees often scale by usage too! So we've got no infrastructure overhead and we're only paying for what we're using.
✅ Minimizing monthly fees
✅ Maximizing time spent shipping features
My Esports & Tech Newsletter comes out every two weeks.
Subscribe if you like code, esports, and all the creative things in between. ✨