I'm glad you've taught yourself infra things as you needed. But, you see, this is an anecdotal proof (like the whole article, anyway).
Learning infra is not the case all the time. Some companies choose AWS (or any other) for speed.
We can, again, argue but the argument is my PoV vs yours, or any other new commenter. Although I know how to maintain small infra: bunch of vms, reverse proxy and an rdbms, I'm not really into hosting HA Rabbitmq or Postgres myself. There is a ton of problems and configuration options coming from replication and consistency I would rather pay premium to people who have done it in the past.
I want my team to build solutions solving customers problems instead of fixing bugs in our replication code. It's all about perspective, I guess we can't reach a definitive answer for one or the other.
You would rather have a team of specialists for every piece of technology you have. I'd rather have my team members not focus on nuissances of database replication, and instead solve our customers' problems.
Looks like both of us are successful. Why does it have to be that there is only one way to success?
There isn't just one way, but from what I can tell AWS works great for the really small and the really big, and is a massive waste of money for the in-between. They have run an amazingly effective marketing campaign to make everyone feel like they are missing out if they aren't using it.
The learning curve for working with AWS is similar to the learning curve of working on bare metal. It honestly does not take a specialist to use MySQL, Postgres, etc. They are really quite easy to make a HA turnkey solution. It's as easy as learning how to effectively use an amazon service. We aren't talking about the days where you had to shard out which was a big pain in the ass, because machines are cheap now with 128 physical cores, 1tb of memory, massive fast storage, etc. You can run the nastiest largest database on a single machine and achieve a pretty large scale doing it.
One of these paths costs about $2500 a month with server purchase amortization, and on the other about $20,000 per month. Either way I need someone to manage it (unless you are talking heroku level of turn-key, then up that $20k a month to $50k a month).
Learning infra is not the case all the time. Some companies choose AWS (or any other) for speed.
We can, again, argue but the argument is my PoV vs yours, or any other new commenter. Although I know how to maintain small infra: bunch of vms, reverse proxy and an rdbms, I'm not really into hosting HA Rabbitmq or Postgres myself. There is a ton of problems and configuration options coming from replication and consistency I would rather pay premium to people who have done it in the past.
I want my team to build solutions solving customers problems instead of fixing bugs in our replication code. It's all about perspective, I guess we can't reach a definitive answer for one or the other.