vturecek

8 ms·

1. 1.▲
   by vturecek 7y ago

   Yes precisely! OAM is meant to provide some consistency and standardization to this practice, while fully expecting each platform to have unique capabilities and requirements that can be surfaced through the model. It's really illumina
2. 2.▲
   by vturecek 7y ago

   Interestingly, what we found through our research was that nobody could agree on a definition of "application" in a microservices world. The way OAM is designed currently doesn't enforce a rigid "application" struct
3. 3.▲
   by vturecek 7y ago

   The overarching idea with OAM is to standardize the model by which applications are composed and operated, regardless of the environment you end up working in. So as you go from one platform to another, you have a consistent experience and
4. 4.▲
   by vturecek 7y ago

   Yeah your understanding is spot on, glad that was helpful! I can imagine platforms choosing to adopt the Kubernetes API for container infrastructure, but it is still the Kubernetes API and it seems like keeping up with changes would be diff
5. 5.▲
   by vturecek 7y ago

   Yup, that's how the Open Application Model is implemented for Kubernetes. The OAM spec format closely resembles the spec format for Kubernetes resources so if you use Kubernetes it should already feel familiar. But it can be implemente