Menu
Microsoft unveils Kubernetes, microservices projects

Microsoft unveils Kubernetes, microservices projects

Dapr and OAM open source projects provide building blocks for microservices and a specification for cloud-native applications

Credit: Microsoft

Microsoft has unveiled two open source projects in the microservices and Kubernetes realms. Dapr (short for distributed application runtime) provides a runtime for microservices, while the Open Application Model, or OAM, offers a specification for running applications on Kubernetes and other platforms.

Dapr is a portable, event-driven runtime intended to make it easier to build microservices-based stateless and stateful applications to be deployed in the cloud or on the edge. It can be used with multiple languages and frameworks and consists of building blocks accessed by standard gRPC or HTTP APIs. The building blocks support best practices, with building blocks currently enabling activities such as service invocation, state management, publish-and-subscribe messaging, and event-driven resource bindings.

[ Microsoft .Net 5 unites the .Net Framework and .Net Core: Find out what the merger of .Net Standard and .Net Core means for developers. | Learn how to get the most from .Net Framework and .Net Core from InfoWorld’s Microsoft Architect blog. | Keep up with hot topics in programming with InfoWorld’s App Dev Report newsletter. ]

Dapr is platform-agnostic, with applications able to be run locally, in a Kubernetes cluster, or in other hosting environments that can integrate with Dapr. This enables developers to build microservices that can run with no code changes in the cloud or edge. Included with Dapr are language-specific SDKs for Go, Java, .Net, Python, and JavaScript. A CLI is included to make it easier to get started. Dapr is available in an alpha release.  

Open Application Model provides a specification for Kubernetes deployments and cloud-native applications. Emphasizing the separation of development and operations concerns, OAM provides a way to describe the components of an application separately from how the application is deployed and managed. This separation of concerns is important because every Kubernetes cluster is different from ingress to CNI (Container Network Interface) to service mesh.

Separating the application definition from operational details allows developers to focus on the key elements of their application rather than the deployment target. The separation of concerns also lets platform architects build reusable components while developers can focus on integrating those components. Platform-agnostic OAM was co-created with Alibaba Cloud under the auspices of the Open Web Foundation.

Getting started with Dapr and OAM

Dapr SDKs and documentation are available on GitHub. OAM can be accessed via GitHub as well.


Follow Us

Join the newsletter!

Or

Sign up to gain exclusive access to email subscriptions, event invitations, competitions, giveaways, and much more.

Membership is free, and your security and privacy remain protected. View our privacy policy before signing up.

Error: Please check your email address.

Tags open sourceMicrosoftKubernetes

Brand Post

Show Comments