Dapr v1.0 Released

With v1.0 release, Dapr applications can now be deployed to self-hosted infrastructure or Kubernetes clusters in production scenarios.

Recently, Microsoft's Dapr(Distributed Application Runtime),  announced the v1.0 release, which has achieved the stability and enterprise readiness to be designated production-ready.

Well, Dapr is an open source, portable, event-driven runtime form Microsoft that makes it easy to build resilient, microservice, stateless and stateful applications that run on the cloud and edge. The solution enables you to focus on writing business logic and not solving distributed system challenges, thereby significantly improving your productivity, and reducing development time. 

Source: Dapr

Distributed Application Runtime lowers the bar for entry to build modern cloud native applications based on a microservices architecture and with this v1.0 release, Dapr applications can be deployed to self-hosted infrastructure or Kubernetes clusters in production scenarios.

The Dapr team said that in the v1.0 release they have focused on Kubernetes as the primary hosting environment to run production applications, and as the platform matures further the team expects to see Dapr in serverless environments.

Kubernetes which is the primary hosting environment in v1.0 is deeply integrated with both the Dapr control plane and Dapr sidecar architecture. Operationally installing and upgrading Dapr to Kubernetes has been made easy with Dapr CLI “init” and “upgrade” commands that pull down the correct Dapr runtime versions. This also ensures that these are rolled out in a controlled manner, including migrating certificates that are in use.

In v1.0 release the actor placement service has a high availability configuration to enhance resilience and enable upgrades on production system that use actors to minimize downtime on actor instance availability. Not only this, all Dapr APIs can now be called on the Dapr sidecar before the app has responded on the app-port.

Now, Http endpoints in your app can also be https endpoints, which previously were blocked.

You can now see version information for each component using the CLI component command dapr components -k. The release also brings support for HTTP query parameters with many values per key, including support in SDKs. 

For additional details, you can visit the release notes here.