From 1ab1d6dca828f33edc0549f00570550235b3b804 Mon Sep 17 00:00:00 2001 From: Cesar De la Torre Date: Tue, 29 Aug 2017 14:41:59 -0700 Subject: [PATCH] Updated 01. Roadmap and Milestones for future releases (markdown) --- ...dmap-and-Milestones-for-future-releases.md | 21 ++++++++++--------- 1 file changed, 11 insertions(+), 10 deletions(-) diff --git a/01.-Roadmap-and-Milestones-for-future-releases.md b/01.-Roadmap-and-Milestones-for-future-releases.md index e1f7d47..0f34a20 100644 --- a/01.-Roadmap-and-Milestones-for-future-releases.md +++ b/01.-Roadmap-and-Milestones-for-future-releases.md @@ -54,22 +54,24 @@ https://github.com/JeremySkinner/FluentValidation - Deployment/support into Kubernetes in Azure Service Fabric (currently only on Windows Containers without RabbitMQ but using Azure Service Bus for messaging/events). +- Azure Storage Blob: Using Azure Blobs to store the Product Images instead of plain files in folders + +- Azure Functions: Azure Function microservice (The Marketing feature has an Azure function returning the Marketing Campaign content) + - DevOps: eShopOnContainers scripts/procedures of CI/CD pipelines in Visual Studio Team Services -vNEXT: +# VNext (To start around October/November 2017) + +Other possible features: +- Azure Event Grid: Implement an additional Event Bus implementation based on Azure Event Grid. +- Azure Functions integrated with Azure Event Grid: Additional event-driven Azure Function microservice (i.e. grabbing uploaded images and adding a watermark and putting it into Azure blobs) - The notification would come from Azure Event Grid when any image is uploaded into a BLOB storage. - Monitoring/Diagnostics of microservices based on Application Insights with custom perfkeys - 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. -- Additional Azure cloud scenarios - 1. Azure Functions: Implement an event-driven Azure Function microservice (i.e. grabbing uploaded images and adding a watermark and putting it into Azure blobs) - 2. Azure Storage Blob: Related to the previous feature - Use Azure Blobs to store the Product Images - 3. Azure App Service: Make the monolithic Web app supporting Azure App Service with Docker - -- 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.0 +- 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. - Security: - Encrypt secrets at configuration files (like in docker-compose.yml). Multiple possibilities, Azure Key Vault or using simple Certificates at container level, Consul, etc. @@ -85,8 +87,7 @@ vNEXT: - (To be Confirmed) Nancy: Add a Nancy based microservice, also with DocDB, etc. -- (To be Confirmed) Service Fabric and Azure version -Actor model, stateful services, etc. +- (To be Confirmed) Service Fabric and Actor model, stateful services, etc. - (To be Confirmed) Guide on Kubernetes • Possible "Getting started guide w/ using minikube and eShopOnContainers" -- For MAC dev machine most of all: [Requirements](https://kubernetes.io/docs/getting-started-guides/minikube/#requirements) • Possible "Examples using https://github.com/kubernetes/helm"