Cloud-native essay dives into our infrastructure

I just wrote an article entitled “Opposite of Cloud Native is?” It’s inspired by how we’re running things here at Talk Python:

There seems to be a lot of contention lately about whether you should go all-in on the cloud or to keep things as simple as possible. Those on the side of “build for the cloud” often frame this as cloud-native. By that, I believe they mean you should look at every single service offered by your cloud provider when architecting your application and generally the more services you pull together the better. … In this essay, I’ll define a new term for the modern opposite of cloud-native. I think you’ll find it appealing.

If that sounds interesting, read the whole article at mkennedy.codes.