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

Updated Roadmap and Milestones for future releases (markdown)

Cesar De la Torre 2017-02-15 14:35:17 -08:00
parent 9d895ff172
commit 03b9df3fcc
1 changed files with 8 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

13
Roadmap-and-Milestones-for-future-releases.md

@ -1,7 +1,10 @@
## Phase 1 Roadmap (By March/April 2017 timeframe) ## Version 0.1 (Current version)
- Migrate projects to .NET 1.1 and EF 1.1 - Docker containers with .NET Core and Linux images support/tested
- Migrate to .csproj and Visual Studio 2017 support, including VS Docker Tooling requirements at the docker-compose.yml files - .NET 1.1 and EF 1.1 support
/////////////////////////////////////////////////////////////////////////////////////////////////////////////////////// - (vs2017 branch) Plus, migrated to .csproj and Visual Studio 2017, including VS Docker Tooling requirements at the docker-compose.yml files
## Version 0.2 Roadmap (By March/April 2017 timeframe)
- Implement support for Windows Containers running on Windows NanoServer using different Docker base images instead of the Linux based images (.NET Core code should be the same as it is cross-platform) - Fork or the same repo? - Implement support for Windows Containers running on Windows NanoServer using different Docker base images instead of the Linux based images (.NET Core code should be the same as it is cross-platform) - Fork or the same repo?
- INTEGRATION EVENTS with Event-Bus implementations: Implement Event-Driven communication between microservices/containers based on Event-Bus interfaces and two implementation: - INTEGRATION EVENTS with Event-Bus implementations: Implement Event-Driven communication between microservices/containers based on Event-Bus interfaces and two implementation:
@ -56,7 +59,7 @@ Our task here will be to use that new lib.
- API versioning Management for microservices. Techniques and things to have into account Related to Caos-Monkey, etc. - API versioning Management for microservices. Techniques and things to have into account Related to Caos-Monkey, etc.
- Solid API contracts (based probably on Swagger, but interoperable with any language and explicit per paramater) - Solid API contracts (based probably on Swagger, but interoperable with any language and explicit per paramater)
## Phase 2 Roadmap (After April 2017) ## Future versions - Roadmap (After April 2017)
- Production-Ready Cloud application with Resilient microservices' design and implementation - Production-Ready Cloud application with Resilient microservices' design and implementation
- 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. - 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.