From d98301b52ed53da49b41be597de22534962fbea6 Mon Sep 17 00:00:00 2001 From: Cesar De la Torre Date: Tue, 29 Aug 2017 14:33:08 -0700 Subject: [PATCH] Updated 01. Roadmap and Milestones for future releases (markdown) --- ...dmap-and-Milestones-for-future-releases.md | 26 +++++++++---------- 1 file changed, 13 insertions(+), 13 deletions(-) diff --git a/01.-Roadmap-and-Milestones-for-future-releases.md b/01.-Roadmap-and-Milestones-for-future-releases.md index 15e3e46..e1f7d47 100644 --- a/01.-Roadmap-and-Milestones-for-future-releases.md +++ b/01.-Roadmap-and-Milestones-for-future-releases.md @@ -45,23 +45,23 @@ https://github.com/JeremySkinner/FluentValidation . Running as a container: https://github.com/dotnet/eShopOnContainers/tree/master/src/Web/WebMonolithic . More advanced layered web app: As segregated project available at: https://github.com/dotnet/eShopOnWeb This app is not using Docker containers, just plain web +- Additional microservice (Marketing and Location microservices) with data stored in MongoDB containers or Azure CosmosDB -## Version 0.3 Roadmap (BETA, by May 2017 timeframe) - -- INTEGRATION EVENTS (Advanced scenario): Proof of concept of an Order-Process SAGA (Pending, Paid, Handling, Shipped, Canceled if timeout because it was not paid, etc.) as a long running process. It is a of a long running instance of a business process (similar to a workflow but implemented as a class with state persistence). The business process would be the "Order-Process-Saga" workflow, involving multiple mock services like PaymentGateway, StockChecking, etc. while changing the Order's state until the order is shipped. Then a background job which fakes ordre delivery and changes order states to delivered. - -- Deployment/support of eShopOncontainers into Kubernetes in ACS, Azure Service Fabric and Docker Swarm. - -- DevOps: eShopOnContainers documentation/procedures of DevOps and CI/CD pipelines in Visual Studio Team Services - -## Future versions - Roadmap (After May 2017) +## Deploying to Azure -- Production-Ready Cloud application with resilient microservices' design and implementation - - Deployment to Orchestrators: Kubernetes, Service Fabric, DCOS, Swarm, etc. - - Monitoring/Diagnostics of microservices based on Application Insights with custom perfkeys +- Deployment/support into Kubernetes in ACS + +- Deployment/support into Kubernetes in Azure Service Fabric (currently only on Windows Containers without RabbitMQ but using Azure Service Bus for messaging/events). + +- DevOps: eShopOnContainers scripts/procedures of CI/CD pipelines in Visual Studio Team Services + + + +vNEXT: +- Monitoring/Diagnostics of microservices based on Application Insights with custom perfkeys - Service Fabric Stateful Service implementation in the SF branch -- Additional microservice with data stored in a No-SQL database like Azure Document DB + - 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. - Additional Azure cloud scenarios