Microservices can be hard. But, while being exceedingly difficult to architect they have become an increasingly popular architecture pattern. As developers begin to migrate from existing monolithic code bases to a microservices system, they spend much of their time dealing with the inherent challenges presented by distributed applications, such as state management and service invocation.
Enter Dapr - A Distributed Application Runtime built with developers in mind. Dapr helps out with some of these problems by providing consistent building blocks in the form of http/gRPC APIs that can be called natively or using one of the language SDKs.
The Cloud Native Global Black Belt (GBB) Team has created this workshop with the hopes of illustrating how microservice development can be made easier with Dapr!
This workshop is:
-
An introduction to Dapr and how it enables developers to build resilient, event-driven, stateful and stateless applications
-
A series of hands-on challenges that allow participants to implement solutions to the problems commonly faced in microservice development
-
A solution that, when completed, provides a set of industry best practices to follow when building distributed systems
This workshop is not:
-
An introduction into microservices or containers
-
A Kubernetes workshop
-
An opportunity to learn new programming languages
This workshop was created for software developers who are looking to gain a deeper understanding of how to build cloud native, distributed applications. Ideally, those looking to participate will have previous hands-on experience with microservice-based applications, however knowledge of the architectural style may also be sufficient.
Experience with the following is required:
- Azure Cloud
- Kubernetes-hosted, containerized applications (any distribution, AKS recommended)
- Software Development with one or more programming languages
Experience with the following is recommended:
- .Net Core, NodeJS, Java or Golang programming languages
Over the period of approximately two days, participants will use a variety of Dapr components to build out and deploy a complete system of microservices that will replace Cloud Coffee Company's core Ordering Platform. The Dapr learning objectives that will be covered are as follows:
| Objective | Description |
|---|---|
| Dapr Local Development | Get Dapr running locally and set-up a local development environment. |
| Pub-sub | Use a Dapr pub-sub component to publish orders to three different subscribers. |
| State & Secret Management | Use Dapr State and Secret building block APIs to store and access data. |
| Service-to-service Invocation | Implement an input binding and service-to-service invocation calls between microservices. |
| Distributed Tracing | Configure and view end-to-end tracing across Dapr components. |
| Output Bindings | Construct storage and SignalR output bindings. |
| Dapr on K8s | Configure and deploy microservices application and all Dapr components onto AKS. |
The diagram below is a depiction of the workshop journey and an overview of the Dapr concepts that will be covered along the way.
NOTE: Challenge 6 is optional, as it does not provide an introduction to any new Dapr concepts, but rather improves the UI. Challenge 7 is a multi-part challenge as it deals with the operationalization of Dapr projects as a whole in Kubernetes.
In order to partake in the workshop, you will be required to install the following technical prerequisites. In order to understand more about the customer backstory, check out the customer story...
This project welcomes contributions and suggestions. Most contributions require you to agree to a Contributor License Agreement (CLA) declaring that you have the right to, and actually do, grant us the rights to use your contribution. For details, visit https://cla.opensource.microsoft.com.
When you submit a pull request, a CLA bot will automatically determine whether you need to provide a CLA and decorate the PR appropriately (e.g., status check, comment). Simply follow the instructions provided by the bot. You will only need to do this once across all repos using our CLA.
This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact opencode@microsoft.com with any additional questions or comments.
Microsoft and any contributors grant you a license to the Microsoft documentation and other content in this repository under the Creative Commons Attribution 4.0 International Public License, see the LICENSE file, and grant you a license to any code in the repository under the MIT License, see the LICENSE-CODE file.
Microsoft, Windows, Microsoft Azure and/or other Microsoft products and services referenced in the documentation may be either trademarks or registered trademarks of Microsoft in the United States and/or other countries. The licenses for this project do not grant you rights to use any Microsoft names, logos, or trademarks. Microsoft's general trademark guidelines can be found at http://go.microsoft.com/fwlink/?LinkID=254653.
Privacy information can be found at https://privacy.microsoft.com/en-us/
Microsoft and any contributors reserve all other rights, whether under their respective copyrights, patents, or trademarks, whether by implication, estoppel or otherwise.