Opposite of Cloud Native Is?
Posted by mikeckennedy@reddit | Python | View on Reddit | 15 comments
Opposite of Cloud Native is? It's time to define what it means to be NOT cloud-native, in a positive way. Here's an essay I wrote today. Would love your thoughts on it.
https://mkennedy.codes/posts/opposite-of-cloud-native-is-stack-native/
Glittering_Peak7233@reddit
The opposite of cloud-native would be on-premises or traditional IT infrastructure, where applications are deployed and run on local servers rather than leveraging cloud environments. Are you exploring different deployment options?
majordouble@reddit
Thanks for the article... it resonated with this hobby developer who wants to get the most out of my time. I'd love to see you expand on this in a Talk Python Training course. There seem to be enough DevOps-related material to make for a great discussion. Derrick
mikeckennedy@reddit (OP)
Thanks Derrick. I'll definitely consider it!
Crossroads86@reddit
I am not sure if I follow. Yes you decluttered a lot of things by leaving out your repositorys, logging, container orchestrstor, queques etc. And you used docker to provide an abstraction laier and scaling. But imo that does not constitute the opposite of cloud native.
Also, for instance plattforms consisting of multiple microservices or apps actually benefit from centralized logs, queues or repositorys instead of each "stack" implementing all of this themselves. I, for example, love aws cloudwatch logs and sqs.
By the way: Love your podcast!
mikeckennedy@reddit (OP)
Hey, first, thanks for the kind words on the show. :)
I didn't leave out much. There is no container orchestrator, no queues, no repositories (other than the source in github). There is no scaling. It's just much bigger than it needs to be and that handles the scale. That's easy to do because the whole server is $25.
I do know that centralized logs are great for microservices. But with just one app, any log you have is centralized. And so on. Cheers.
mikeckennedy@reddit (OP)
u/Crossroads86 I thought about this a bit more and this is probably the best way to present the idea I'm advocating. It's not whether kubernetes or serverless is bad (or good). But rather that whatever you come up with should probably fit on a single server and be portable. If you wanted PaaS as your style, then that'd be great. Just consider hosting your own mini-PaaS with Cooify which is a very neat project. Or if you want serverless, consider putting them on your own serverless platform you control rather than tying into AWS or Azure too deeply. If Kubernetes is the vibe, then run a cluster yourself.
It may or may not resonate but that's the essence of the article I think.
Crossroads86@reddit
Apprecite the reflection!
Candid-Ad9645@reddit
“Cloud native” is a term from kubernetes. It usually means that the tool has a k8s operator, easy to run docker image, or is a CNCF sponsored project. It’s not software that runs on literally any cloud provider’s platform.
mikeckennedy@reddit (OP)
Cloud native is a term for a certain style of architecture. It may be also some product from Kubernetes I've been ignoring. For example, from Microsoft ( https://learn.microsoft.com/en-us/dotnet/architecture/cloud-native/definition )
"Cloud-native architecture and technologies are an approach to designing, constructing, and operating workloads that are built in the cloud and take full advantage of the cloud computing model."
and
"Cloud-native systems take full advantage of the cloud service model. Designed to thrive in a dynamic, virtualized cloud environment, these systems make extensive use of Platform as a Service (PaaS) compute infrastructure and managed services."
And from Google, https://cloud.google.com/learn/what-is-cloud-native
Cloud native definition
Cloud native means adapting to the many new possibilities—but very different set of architectural constraints—offered by the cloud compared to traditional on-premises infrastructure.
Unlike monolithic applications, which must be built, tested, and deployed as a single unit, cloud-native architectures decompose components into loosely coupled services to help manage complexity and improve the speed, agility, and scale of software delivery.
Candid-Ad9645@reddit
Literally from that Microsoft article:
The term “cloud native” grew in popularity with kubernetes and the CNCF (Cloud Native Computing Foundation).
If you want to learn about cloud native architectures and teach about them via your blog, then ignoring kubernetes is a huge mistake.
MethClub7@reddit
I literally could not care less about your blog.
Crossroads86@reddit
Same! I always read topics on comment on stuff I absolutely do not care about!
MethClub7@reddit
Good for you, turbo. Now go gargle OPs testicles in a cloud computing sub, not a python one.
unfair_pandah@reddit
I would've though the opposite of Cloud Native is punch cards or something...
mikeckennedy@reddit (OP)
Ha. See the definition from Google: https://cloud.google.com/learn/what-is-cloud-native