Here’s an article I stumbled upon that describes an infrastructure stack for a new SaaS product:
Before you can launch a new service, you need infrastructure. You want reliability, scalability, and many other -ilities. But you don’t want to break the bank.
I’ve gone through the process of launching several new services over the past few years. Each time, I’ve explored the field of options.
The goal of this article is to help you focus on the value that your solution provides to your users, while minimizing the time and money spent geeking out on infrastructure.
The choices are pretty good, I think.