Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

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

oam.dev

Post reply on HN
Print view View original

21–30 of 47 posts

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

#21

Post by fengjingchao »

tmpz22 wrote: post #16
linkdd wrote: post #15

Earlier quoted context omitted.

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.

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.

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.

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

#22

Post by fengjingchao »

jimmyed wrote: post #18
falcolas wrote: post #2

An abstraction (OAM) On the top of an abstraction (K8s Custom Object specification) On the top of an abstraction (Kubernetes, et.al.) On top of another abstraction (Containers) On top of another abstraction (VMs) I wonder if the Dyke-sealing-boy is available for the inevitable leaks? On a slightly more serious note, even though I participated in OAM early in the process, I've never really seen the value in the abstra…

Reminds me of SICP.

If we all use LISP the whole tech stack would be much simpler :)

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

#23

Post by fengjingchao »

outside1234 wrote: post #3

Don't get it. Seems like someone is trying to make Kubernetes work on Service Fabric or something.

Not make k8s work on service fabric. It is to provide a common platform so that the community users could build their own service fabric in an easier way.

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

#25

Post by jjacobson93 »

falcolas wrote: post #2

An abstraction (OAM) On the top of an abstraction (K8s Custom Object specification) On the top of an abstraction (Kubernetes, et.al.) On top of another abstraction (Containers) On top of another abstraction (VMs) I wonder if the Dyke-sealing-boy is available for the inevitable leaks? On a slightly more serious note, even though I participated in OAM early in the process, I've never really seen the value in the abstra…

Computer science is all about abstractions. You can keep on going down with your examples: VMs are an abstraction on top of an operating system, which is an abstraction on top of virtual memory, on top of a physical machine...

Just like Python is an abstraction on top of C, which is an abstraction on top of assembly language, which is an abstraction of a CPU and memory, etc.

There’s reasons for all of the abstractions.

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

#26

Post by resouer »

tmpz22 wrote: post #11
linkdd wrote: post #7

Earlier quoted context omitted.

Imagine a developer: > On top of another abstraction (VMs) Who does not need to badly handle infrastructure > On top of another abstraction (Containers) Who does not need to badly handle isolation > On the top of an abstraction (Kubernetes, et.al.) Who does not need to badly handle scalability > On the top of an abstraction (K8s Custom Object specification) Who does not need to badly handle deployment > An abstractio…

> Who just wants to ship their code That exists, its called a PaaS. Kubernetes was not meant to be a PaaS. I'm starting to think people create these orgs to forward their own career, products, or companies.

Kubernetes + OAM = PaaS the better way

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

#27

Post by resouer »

outside1234 wrote: post #3

Don't get it. Seems like someone is trying to make Kubernetes work on Service Fabric or something.

Actually it will be interesting to see k8s work on service fabric, though it seems SF itself is not interested in this (it's not even quite alive).

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

#28

Post by notmars »

Oh the longing and despair of missing Docker Swarm... It was missing so little...it was so well done and simple, elegant. Docker Swarm is now the betacam of container orchestration solution. hopefuly all these layers (kube-> custom kube -> OA*) will soon converge and fold themselves into something grandiose, efficient and simple. How eager I am to be there :-)

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

#29

Post by resouer »

fengjingchao wrote: post #22
jimmyed wrote: post #18

Earlier quoted context omitted.

Reminds me of SICP.

If we all use LISP the whole tech stack would be much simpler :)

Agree. I must thank OSI layers model, so I don't need to program against TCP packets ...

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

#30

Post by resouer »

falcolas wrote: post #2

An abstraction (OAM) On the top of an abstraction (K8s Custom Object specification) On the top of an abstraction (Kubernetes, et.al.) On top of another abstraction (Containers) On top of another abstraction (VMs) I wonder if the Dyke-sealing-boy is available for the inevitable leaks? On a slightly more serious note, even though I participated in OAM early in the process, I've never really seen the value in the abstra…

Complaining OAM should not be implemented on K8s doesn't make sense to me.

Kubernetes is NOT a PaaS, it's by design for you to create abstractions atop and serve your own purposes. And OAM is a great option if you want to build things like app PaaS or app delivery systems with k8s.

It seems you either have mis-understanding on OAM or Kubernetes, based on you are involved in OAM, it's likely the later case.

Post reply on HN