I get how recommending using a stack from last decade will make sense for some. Lambdas and NoSQL may seem like over kill for a simple SaaS project but Uclusion has found the water is warmer on the AWS side then your blog is indicating.
For one thing relational databases are an immense pain to control the schema of. Also Lambdas versus monolith is not the same as micro-services versus monolith. To build a Rest API an API Gateway plus Lambdas is just faster then the majority of monolith platforms. The technologies you are talking about using not only don't scale - they might actually be slower to develop on as well.
Again I understand the points made in your blog but I think there is more of a choice to be made than you indicate. I'd love to compare notes to know what development time and outcomes on a non AWS stack looks like. I'm certain your advice was correct in the past but as AWS gets better I'm not certain ignoring it even for a simple SaaS project is still correct.
Hi Tomas,
I get how recommending using a stack from last decade will make sense for some. Lambdas and NoSQL may seem like over kill for a simple SaaS project but Uclusion has found the water is warmer on the AWS side then your blog is indicating.
For one thing relational databases are an immense pain to control the schema of. Also Lambdas versus monolith is not the same as micro-services versus monolith. To build a Rest API an API Gateway plus Lambdas is just faster then the majority of monolith platforms. The technologies you are talking about using not only don't scale - they might actually be slower to develop on as well.
Again I understand the points made in your blog but I think there is more of a choice to be made than you indicate. I'd love to compare notes to know what development time and outcomes on a non AWS stack looks like. I'm certain your advice was correct in the past but as AWS gets better I'm not certain ignoring it even for a simple SaaS project is still correct.