Versioning Microservices
Versioning Microservices, Complete guide to build enterprise edition application end to end.
Microservices are a design pattern in which applications are composed of independent modules that communicate with each other within well defined boundaries. This makes it easier to develop, test, and deploy isolated parts of your application. If you are coming on this course directly, I suggest follow the Learning path as mentioned below to understand the entire picture.
1. Getting Started with Microservices using Clean Architecture
2. Securing Microservices using Identity Server 4
3. Implementing Cross Cutting Concerns
4. Versioning Microservices (Current Course)
5. Building Angular Application for MicroServices
6. Deploying Microservices to Kubernetes and AKS
In the earlier section, you would have already learnt plethora of technologies while designing Microservices and implementing Identity Server. During that learning journey you must have designed Microservices module using clean architecture. While doing so, You would have also implemented CQRS design pattern in order to implement the clean architecture design. Here, you will learn how to apply all the industry best practices together. This series is designed using .Net Core 6 and Angular 15. Angular is used in the client application. For that there is a separate dedicate course for that.
This course is part of Microservices series where in you will learn all minute details related to Microservices. During this learning path, you will learn how to connect the dots using different technologies and tooling. This course “Versioning Microservices” is the fourth edition of the series. In this course you will learn all different types of versioning strategy in depth. At the same time you will understand how to keep clients backward compatible with the support of different versions. In this course, you will be implementing following things:
Coupon Code:- 791ACCB4E85BAD2E955E
- Introduction
- Introduction
- Architecture Overview
- Versioning Strategy
- Branching Strategy
- Implementing API Versioning
- Let’s understand what to change
- Implementing Basket Checkout V2 Version
- Getting 400 Validation Error with Checkout
- Creating V2 Version of Basket Controller
- Configure Swagger Options
- Applying Swagger Default Values
- Custom Swagger Configuration in Startup
- Testing new version of Swagger
- Creating new version of Basket Checkout method
- Creating V2 version of Basket Ordering Consumer
- Configuring new Receive EndPoint for Checkout V2
- Checkout Order Command Fluent Validation Failing
- Fixing Checkout Issue
- What’s Next
- What’s Next
