From 29aaa7defb67c04f49ce6105f24c390989910ae4 Mon Sep 17 00:00:00 2001 From: Cesar De la Torre Date: Tue, 16 May 2017 13:23:16 -0700 Subject: [PATCH] Updated 01. Roadmap and Milestones for future releases (markdown) --- 01.-Roadmap-and-Milestones-for-future-releases.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/01.-Roadmap-and-Milestones-for-future-releases.md b/01.-Roadmap-and-Milestones-for-future-releases.md index 33443b9..e0f28d2 100644 --- a/01.-Roadmap-and-Milestones-for-future-releases.md +++ b/01.-Roadmap-and-Milestones-for-future-releases.md @@ -1,4 +1,4 @@ -## Version 0.2 (BETA, current version - April 2017) +## Version 0.2 (BETA, current version - May 2017) - Available at the MASTER branch. - Docker containers with .NET Core and Linux images support/tested. Windows Containers are work-in-progress. @@ -7,7 +7,7 @@ - CLI build process using a Docker ASPNETCore build-image (microsoft/aspnetcore-build) with all the needed SDKs so the compilation takes place in the same container recommended to be used in your CI pipeline (Continuous Integration). No need to have all dependencies in the dev machine when using this method. [Using this CI docker-compose file](https://github.com/dotnet/eShopOnContainers/blob/master/docker-compose.ci.build.yml). - Initial basic foundational microservice oriented architecture, easy to get started, described in this **Guide/eBook** (Early DRAFT, still work in progress). -- Support for Windows Containers running on Windows Server Nano using different Docker base images instead of the Linux based images +- Support for Windows Containers running on Windows Server Nano using different Docker base images instead of the Linux based images - INTEGRATION EVENTS with Event Bus implementations: Implement Event-Driven communication between microservices/containers based on Event Bus interfaces and two implementations: 1. (Implemented as PoC) Standalone Pub/Subs messaging implementation based on an out-of-proc RabbitMQ Container