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

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 :-)

Hi, OAM and KubeVela author here.<p>We originally created these specification and projects to facilitate delivering applications to Kubernetes without exposing all the nitty-gritty details. There&#x27;s a lot to do to achieve such goal besides managing application templates, clusters, environments, cloud resources and service bindings, etc. We have seen common patterns rising up within companies of medium and large sizes. That&#x27;s why we created them to provide common platform for others to build their own application platforms.<p>Let me know if you have any questions and I will be available here to answer them.

The spec doesn&#x27;t appear to address the 12-factor app spec which does a similar job in a more general way.<p><a href="https:&#x2F;&#x2F;github.com&#x2F;oam-dev&#x2F;spec&#x2F;search?q=12+factor" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;oam-dev&#x2F;spec&#x2F;search?q=12+factor</a><p><a href="https:&#x2F;&#x2F;12factor.net&#x2F;" rel="nofollow">https:&#x2F;&#x2F;12factor.net&#x2F;</a>

I really like this approach for simplifying Kubernetes. A few projects similar to OAM in that it provides a higher level &quot;Application&quot; CRD:<p><a href="https:&#x2F;&#x2F;github.com&#x2F;vmware-tanzu&#x2F;carvel-kapp" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;vmware-tanzu&#x2F;carvel-kapp</a><p><a href="https:&#x2F;&#x2F;github.com&#x2F;k11n&#x2F;konstellation" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;k11n&#x2F;konstellation</a><p><a href="https:&#x2F;&#x2F;github.com&#x2F;kalmhq&#x2F;kalm" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;kalmhq&#x2F;kalm</a> (We ended using this one, which came with a set of matching web UI)

There&#x27;s a K8s implementation of OAM called KubeVela (<a href="https:&#x2F;&#x2F;github.com&#x2F;oam-dev&#x2F;kubevela" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;oam-dev&#x2F;kubevela</a> )

Don&#x27;t get it. Seems like someone is trying to make Kubernetes work on Service Fabric or something.

It should be named Open Kubernetes Application Model. If I&#x27;m understanding correctly, it should be &quot;portable&quot; to other orchestrators or even bare metal. However, it seems to be quite leaky of the underlying Kubernetes stuff.

<a href="https:&#x2F;&#x2F;12factor.net&#x2F;" rel="nofollow">https:&#x2F;&#x2F;12factor.net&#x2F;</a>

Edit: Yep, wrong thread, thanks.

An abstraction (OAM)<p>On the top of an abstraction (K8s Custom Object specification)<p>On the top of an abstraction (Kubernetes, et.al.)<p>On top of another abstraction (Containers)<p>On top of another abstraction (VMs)<p>I wonder if the Dyke-sealing-boy is available for the inevitable leaks?<p>On a slightly more serious note, even though I participated in OAM early in the process, I&#x27;ve never really seen the value in the abstraction it provides, especially since it&#x27;s using the Kubernetes Custom Object Model to run on Kubernetes (first, not only, I know).