| Or you go for even smaller use cases. I host some stuff for some companies to share business information with external suppliers for example. These apps serve < 100 users a month. Still, they all get a load balance configuration to grab the free TLS certs with auto renewal while keeping configuration simple. While I would not recommend premature TLS termination for critical business data, it is sufficient for many applications. Admins get their familiar AWS console to configure the apps and I can make sure these are bundled in a way to be deployed on many different systems. If I wanted to, I could use AWS identity provider like cognito and have it all in one place. I think the main argument for cloud provider is the utility and convenience they provide for small projects. While I do not like the business practices of Amazon and would never like to work for them on AWS, I am also lazy and cannot say I that they didn't develop something very useful. Generally companies don't really care if a solution is 70$ or 3,50$ a month. They do care about my wage much more. Unjustifiable! Sure, you could dump it all on a server somewhere without using any external micro services. But in my experience these project are much more likely to start to randomly haunt you from the past. And worse, I so actually have to maintain the servers. And the price difference for inefficiently used services is mostly between 5$ and 15$. But these extra 10$ a month can easily be set off for reduced development or administration time. If after ~40 years the service is still active, I would freely admit to that mistake. Granted, this isn't applicable for application that do actually need to be scaled. But the time to launch for standard solutions that nudge a few bits here and there can be reduced quite a bit thanks to infrastructure like this. And it may be in use anyway since all the Google Home/Alexa IOT stuff. |