ayan.poddar/eShopOnContainers
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

Updated 01. Roadmap and Milestones for future releases (markdown)

Cesar De la Torre 2018-04-05 13:11:42 -07:00
parent 217cc67fba
commit db1588f43c
1 changed files with 4 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
01.-Roadmap-and-Milestones-for-future-releases.md

@ -3,7 +3,7 @@
* [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.0 (Based on .NET Core 2.0)
## Version 2 (Based on .NET Core 2.0)
- Available at the DEV and MASTER branch.
- Docker containers with .NET Core, Linux images and Windows containers supported and tested.
@ -12,6 +12,8 @@
- 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).
- Microservice oriented architecture, easy to get started, described in this <a href='https://aka.ms/microservicesebook'>Guide/eBook </a>.
- Implementation of the [API Gateway and BFF (Backend-For-Front) patterns](http://microservices.io/patterns/apigateway.html) so you can filter and publish simplified APIs and URIs and apply additional security in that tier while hiding/securing the internal microservices to the client apps or outside consumers. These sample API Gateways in eShopOnContainers are based on [Ocelot](https://github.com/ThreeMammals/Ocelot), an OSS lightweight API Gateway solution explained [here](http://threemammals.com/ocelot).
- 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:
@ -92,11 +94,8 @@ Other possible features:
- (To be Confirmed) Support other DataProtection providers such as AspNetCore.DataProtection.ServiceFabric
- (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"
• Possible "Getting started guide w/ local dev Kubernetes integrated to Docker for Windows and Mac"
- (To be Confirmed) In the Windows Containers fork, implement and add a simple WCF microservice/container implementing any logic like a simulated legacy Payment Gateway, as an example of "lift and shift" scenario.