From 76fcacce91450fb82a5f8b90af07e054a8690c8d Mon Sep 17 00:00:00 2001 From: Cesar De la Torre Date: Tue, 12 Jun 2018 13:25:28 -0700 Subject: [PATCH] Updated 01. Roadmap and Milestones for future releases (markdown) --- ...admap-and-Milestones-for-future-releases.md | 18 ++++++++++++++---- 1 file changed, 14 insertions(+), 4 deletions(-) diff --git a/01.-Roadmap-and-Milestones-for-future-releases.md b/01.-Roadmap-and-Milestones-for-future-releases.md index 2cef44b..d4edb97 100644 --- a/01.-Roadmap-and-Milestones-for-future-releases.md +++ b/01.-Roadmap-and-Milestones-for-future-releases.md @@ -3,6 +3,14 @@ * [https://github.com/dotnet-architecture/eShopOnContainers/blob/dev/branch-guide.md](https://github.com/dotnet-architecture/eShopOnContainers/blob/dev/branch-guide.md): Branches used and their purpose. Any branch not listed in this file is "temporary" and "unsupported" and can be deleted at any time. +## Version 2.1 (Current version based on .NET Core 2.1) +Features supported on v 2.0 listed below, plus the following features: + +- Use of HttpClientFactory with Polly integration for resilient Http communication (Retries with exponential backoff and Circuit Breakers) + +- Real time communication: SignalR Hub microservice/container for real-time communication. Scenario: Notification of Order's status changes. This is new since SignalR is provided in ASP.NET Core 2.1. + + ## Version 2 (Based on .NET Core 2.0) - Available at the DEV and MASTER branch. @@ -70,6 +78,12 @@ Other possible features, to be evaluated for the backlog: - Helm support for Kubernetes deployment and Azure Dev Spaces compatibility +- Support for Service Fabric Mesh (codename "SeaBreeze") + +- Manage Secrets with Azure KeyVault + +- Split Unit Test projects and distribute across microservices, so each microservice "owns" its own tests. + - Implement a more advanced versioning system based on [aspnet-api-versioning](https://github.com/Microsoft/aspnet-api-versioning) or comparable system. Current API versioning is very basic, simply based on the URLs. https://github.com/Microsoft/aspnet-api-versioning @@ -80,8 +94,6 @@ https://github.com/Microsoft/aspnet-api-versioning - Service Fabric Stateful Service implementation in the SF branch - Gracefully stopping or shutting down microservice instances - Implemented as an ASP.NET Core middleware in the ASP.NET Core pipeline. Drain in-flight requests before stopping the microservice/container process. -- Real time communication: SignalR Hub microservice/container for real-time communication, like notificating something important that just happened to the user. This feature needs to wait for SignalR to be available in .NET Core 2.1. - - (To be Confirmed) Support for .NET Core 2.0 Razor Pages as additional client app. - Security: @@ -142,8 +154,6 @@ References on Composite UI with microservices: - Add a Jitter strategy to the Retry policy, check [issue #188](https://github.com/dotnet-architecture/eShopOnContainers/issues/188) for details. - It would probably be a good idea to use the new [HttpClientFactory](https://blogs.msdn.microsoft.com/webdev/2018/04/12/asp-net-core-2-1-0-preview2-now-available/), with Polly integration. - - Increase the resilience of the RequestProvider class in the mobile app, check [issue #206](https://github.com/dotnet-architecture/eShopOnContainers/issues/206) for details. - Investigate using the OIDC library to communicate with IdentityServer from the Xamarin client, check [issue #215](https://github.com/dotnet-architecture/eShopOnContainers/issues/215) for details.