Amazon services are individually not that great in many cases. Their strength is the enormous diversity in the aggregate. You might use your own services for data and apps, but if it's all glued together with Lambda you aren't going anywhere.
Which is exactly why you shouldn't adopt serverless. It's a boondoggle lock-in trick.
If it were an open and widely supported standard it would be a different story.
This is literally what knative is. I don’t know the AWS world at all but at least in GCP their main ideas of serverless are:
1. Knative: open source standards based serverless platform that’s in the process of making its way into the CNCF. I assume this is what Fargate is on AWS? 2. Cloud functions which is also something that you can drop into AWS, Azure, open shift etc..
Re:The Impending Cloud Reshuffle
by tatersolid on Friday December 03, 2021 @10:24PM
(#29438410)
> I think AWS knows that the best it can do is offer so much combined value that people don't want to leave the ecosystem.
This is exactly the Microsoft playbook.
If you can get the same value from another ecosystem, you might leave for a better price. If you can't get the same value from another ecosystem, you won't leave. If you're locked into proprietary AWS systems, it might require a lot of work to migrate.
I do get where the author is coming from with RedShift and Snowflake. I think it's reasonable to look at AWS's data warehouse position and Snowflake's success and see a bit of a failure on AWS's part. However, I think that Snowflake represents a threat to AWS. If all services above the infrastructure became like Snowflake, I could more easily move from AWS to GCP or Azure.
I'd note that it isn't just about companies who will switch cloud providers. It's about whether a company can credibly threaten that they might switch cloud providers. If I'm negotiating with AWS and they see that I'm using SQS, Lambda, RedShift, Timestream, Kenesis, and other proprietary AWS stuff, they know that my threat to leave AWS is hollow. I'd have to rewrite too much infrastructure. Sure, maybe I could replace SQS with Kafka, but it isn't a drop-in replacement. Sure, there are other time-series databases than Timestream, but it's going to require engineering time to migrate.
Yes, even in a world where all the software is the same on top of the infrastructure, it would take time and money to migrate to a different cloud, but it would be less time and money. That "less time and money" means that AWS needs to be more price competitive and it gives me more negotiating power. The harder it is to leave AWS, the more leverage that Amazon has in negotiations. Companies like Spotify and Snap spend hundreds of millions on their cloud services each year. They ink major deals that they negotiate. If they rely on lots of proprietary AWS or GCP systems, it makes it a lot harder to leave - which leave the cloud provider with the leverage when the contract comes up for renewal.