The interesting function therefore is the red line, the one that adds the up-front invest to the potential liability. That's your total cost and the thing you should be minimizing. In most cases, with increasing up-front invest, you'll move towards an optimum range. Additional investment into reducing lock-in actually leads to higher total cost. The reason is simple: the returns on investment diminish, especially for switches that carry a small probability. If we make our architecture ever-so-flexible, we are likely stuck in this zone of over-investment. The Yagni (you ain't gonna need it) folks may aim for the other end of the spectrum - as so often, the trick is to find the happy medium.
Why is AWS losing market share to Microsoft and Google? Probably because cloud cost optimisation and shift towards new type of workloads is hitting the biggest player the most.
Around 40-50% of AWS revenue comes from EC2, the most basic compute offering. This is a higher share than for Azure and GCP. Computing is the easiest cost to optimize, therefore hurting AWS the most. Google Cloud with focus on Data/AI has been consistently taking the market share from AWS/Azure and will soon have 20% of the Cloud market.
Cloudflare serves around 20% of the web with 46 million requests a second.
Surely they must have a lot of data.
Where do they store it?
Plain old PostgreSQL. 🐘
Around 15-20 clusters of them.
Each cluster... See more
As a result of the change to BSL, there is now no certainty with using Terraform:
If you’re a CTO, and you’re picking an IaC tool to use at your company, if you see that Terraform is BSL licensed, why take the risk? You’re now much more likely to go with alternative tools that are truly open source and have no licensing headaches.