In addition, kubernetes is going to start squeezing aws’s profit margins, particularly ec2 as people move to commodity k8s hosting.
In addition, kubernetes is going to start squeezing aws’s profit margins, particularly ec2 as people move to commodity k8s hosting.
Also, AWS moves faster than web tech on the whole, so even if the general shift to k8s continues, AWS will be there to make it easier than rolling your own, and at a price point that's "worth it."
The service layer is just an add-on. Part of their premium. Even if you go full open source you still need infrastructure to run it and that's exactly what companies don't want to do and won't do anymore, and the reason why AWS and Azure are massively successful.
I'm only a developer so I'm sure I'm missing Operations and Business perspectives. Would love to learn more.
You pay $.09 an hour more for an RDS m5.large than you do for an EC2 m5.large. What kind of DBA can you get for $67 a month? That’s maybe one hour of a good DBA’s time per month, tops.
Now, someone will correctly point out that you can run way more compute on a colo’d server than an EC2 instance and they’d be right. But when you realize you’re paying AWS for hypervisor patching, network automation - I’ve worked in places where a security group change in AWS was equivalent to a two week servicenow ticket with the network team - ...
The business perspective to AWS is that you bake operational costs into the product and stop paying people that generate those costs. Not good for sysadmins who aren’t willing to change, but it’s where we are. And it’s why you can’t just say “open source makes this convertible without difficulty” - somebody’s still gotta manage those services ;)
Have you looked at the different TF provisioners? They are all provider specific.
There are a lot of services on AWS that are specific to AWS that you would need to rearchitect your system to use. Even something as simple as an ETL process that lets you load directly from S3 into Redshift and Aurora.
In terms of the cutting edge of bringing "declarative, Kubernetes-style APIs to cluster creation, configuration, and management" see https://github.com/kubernetes-sigs/cluster-api
Unless you build your service like that from the start (e.g.: prematurely optimize, which practically no successful company has the chance to do), you will experience some amount of AWS lock-in.