|Image Credits: https://www.redhat.com/en/topics/cloud-computing/what-is-paas|
Are you a startup? Got a lean and mean team of developers wanting to deploy your apps in AWS Cloud? Are you cost conscious?
Unless you are a sysops yourself and that you are at home with AWS cloud, don't use IaaS of AWS; instead use PaaS of AWS.
And that means don't try to deploy your apps on EC2 by setting up your own VPC and configuring a whole suite of things. Instead make use of AWS BeanStalk. And there again, make sure you don't tie your RDS with your environment life-cycle, when it comes to production environment.
Overlook this advice, and your startup could end-up in the list of those that died before they were launched. This advice holds good if you don't have an exclusive #SysOpsAdmin for #Cloud. If you cut your costs here, you will end up burning your back to say the least.
A tad bit more details:
If application development is one kind of a beast, managing infrastructure is altogether another kind. I have come across many founders that under-estimate tech challenges calling it as not being a rocket-science in spite of going through mounting challenges blaming it on the dev-team. Little do they know that the developer-ego is bigger than that of a founder-ego, and so (s)he will call the infrastructure management an easy-peasy thing. The catastrophic effect of this is that the team ends up embracing cloud as IaaS provider. Without knowing the contemporary better-practices, they end up leaving gaping holes in the system to be exploited by a hacker and thus receiving a shocking monthly bill from AWS. There is no point blaming AWS as being pricey hiding your idiocy.
So here is my first-principle that should be yours as well when it comes to making technology decisions: Your choice of technology (be it the platform, the programming language, the architecture, the tools or even the framework) should be a reflection of your team's strength.
Let me say it louder again,
Your choice of technology should be a reflection of your team's strength.So a recipe that comes out of that first-principle in this situation would be:
If you got a SysAdmin embrace Iaas, else be wise enough to embrace PaaS.Further motivation for your prosperity: With IaaS, you end up managing 5 ever-evolving parts. With PaaS you will end up managing just 2 ever-evolving parts. For the moving parts, see the article banner picture.