Updated 01. Roadmap and Milestones for future releases (markdown)
parent
805b7863fd
commit
f8d7ac1578
@ -65,6 +65,8 @@ We should probably implement Domain Events when implementing the SAGA example pl
|
|||||||
- Use a new Health Check Library (Preview) to be provided by the .NET Team. That library provided by the .NET team will provide: A model of healthcheckresults, A Middleware to return ok/bad, A polling service calling the healthchek service and publishing results (open/pluggable to orchestrators, App Insights, etc.)
|
- Use a new Health Check Library (Preview) to be provided by the .NET Team. That library provided by the .NET team will provide: A model of healthcheckresults, A Middleware to return ok/bad, A polling service calling the healthchek service and publishing results (open/pluggable to orchestrators, App Insights, etc.)
|
||||||
Our task here will be to use that new lib.
|
Our task here will be to use that new lib.
|
||||||
|
|
||||||
|
- Create a building block to handle Idempotency in a generic way ([Issue 143](https://github.com/dotnet/eShopOnContainers/issues/143))
|
||||||
|
|
||||||
- Topics to Review and document:
|
- Topics to Review and document:
|
||||||
- API versioning Management for microservices. Techniques and things to have into account Related to Chaos Monkey, etc.
|
- API versioning Management for microservices. Techniques and things to have into account Related to Chaos Monkey, etc.
|
||||||
- Solid API contracts (based probably on Swagger, but interoperable with any language and explicit per paramater)
|
- Solid API contracts (based probably on Swagger, but interoperable with any language and explicit per paramater)
|
||||||
|
Loading…
x
Reference in New Issue
Block a user