Open Application Model – An open standard for defining cloud native apps

Re:Open Application Model – An open standard for defining cl... by tmpz22 on Friday March 19, 2021 @08:55PM (#26519774)

K8s is one of many options to collaborate and scale applications and for many organizations it is not the best option. It also comes with lots of vendor lock-in if you're using a service like GKE, EKS, or AKE, or integrate with any of their loadbalancer or storage solutions!

Oracle and Alibaba building a large abstraction on top of kubernetes, to do something kubernetes was not designed to do (though capable of doing), is not the direction I personally believe distributed systems development should standardize around.

There are tons of self-hosted PaaS options that are not built on top of massive abstractions and provide better functionality to their users. Since you mentioned Heroku i'll mention https://github.com/dokku/dokku.

[ Parent | on HN ]

Re:Open Application Model – An open standard for defining cl... by resouer on Saturday March 20, 2021 @01:09AM (#26520924)

Actually, almost every big company built massive abstractions on top of Kubernetes and it is what Kubernetes is designed to do (and good at).

That's why if you had a chance to look at Dokku and any other "better" self-hosted PaaS offerings, they are dead. Ppl today choose to use Kubernetes to build abstractions atop and OAM is a battle tested option to achieve this with better clarity and interpretability. Many companies are shifting away from Cloud Foundry and OpenShift to this approach.

[ Parent | on HN ]

Re:Open Application Model – An open standard for defining cl... by linkdd on Friday March 19, 2021 @08:58PM (#26519791)

Yes K8s is one of many options, but one that can translate to many situations. I'd still choose it over anything else when I need more than a `docker run` on a server.

Thanks for the link btw.

[ Parent | on HN ]

Re:Open Application Model – An open standard for defining cl... by tmpz22 on Friday March 19, 2021 @09:04PM (#26519818)

No worries and maybe I am being harsh here but this whole thing seems like a couple big providers trying to push their own idioms on the DevOps industry, an industry which is already saturated on dishonest marketing kool-aid.

"Our solution is way better then all those pre-existing solutions!".

No. No it isn't. Stop acting like you're helping me when you're really selling me something.

[ Parent | on HN ]

Re:Open Application Model – An open standard for defining cl... by fengjingchao on Friday March 19, 2021 @11:28PM (#26520585)

Hi there. I think every open source project is trying to push "their own idioms" to the community. But good open source projects provide good technology directions and generic abstractions to reuse, not dishonest marketing. I suspect that marketing would not work if the project is not good -- people are really smart when choosing projects.

[ Parent | on HN ]

Re:Open Application Model – An open standard for defining cl... by resouer on Saturday March 20, 2021 @01:51AM (#26521061)

There's no such industry named "build app-centric platforms".

[ Parent | on HN ]

Re:Open Application Model – An open standard for defining cl... by tmpz22 on Saturday March 20, 2021 @03:07PM (#26525301)

The shoveling of "Cloud Native" is in part a bid to sell cloud services at AWS, Azure, GCP, Oracle, Alibaba, etc. Just because the engineers on the ground doing the work conveniently ignore this point doesn't mean that the executives who ultimately green light and fund these projects aren't considering it the #1 priority.

[ Parent | on HN ]

Re:Open Application Model – An open standard for defining cl... by resouer on Sunday March 21, 2021 @12:51AM (#26528208)

More and more applications will be built on cloud with or without "cloud-native", we can't stop this trend or arguing technologies that intend to make this process smoother/easier.

And yes I agree those cloud providers will make more money with this trend.

[ Parent | on HN ]