From 06b3b550c209736b6b5844ba57931b8e49ab9a21 Mon Sep 17 00:00:00 2001 From: Cesar De la Torre Date: Thu, 2 Mar 2017 11:55:11 -0800 Subject: [PATCH] Updated 01. Roadmap and Milestones for future releases (markdown) --- 01.-Roadmap-and-Milestones-for-future-releases.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/01.-Roadmap-and-Milestones-for-future-releases.md b/01.-Roadmap-and-Milestones-for-future-releases.md index 96ca891..c931c34 100644 --- a/01.-Roadmap-and-Milestones-for-future-releases.md +++ b/01.-Roadmap-and-Milestones-for-future-releases.md @@ -14,6 +14,10 @@ Two integration event scenarios to implement in the app: 1. Simple (higher priority): Change Product info (name, image URL, etc.) in the Catalog and update that in the existing Orders and Baskets (all, except the price) 2. Complex: Events propagating Order's states changes related to the Order-Process SAGA (InProcess, Paid, Handling, Shipped, Canceled if timeout because it was not paid, etc.) - Scenario to be discussed/defined +- Implement security best practices about app's secrets (conn strings, env vars, etc.) + (However, this subject depends on the chosen orchestrator...) + See when using Swarm: https://blog.docker.com/2017/02/docker-secrets-management/ + - Monolithic ASP.NET MVC app with public area of the eShop (Home page with catalog-view functionality, basically). As out of band, separate project (same GitHub repo but separate folder and separate solution) - WebForms client (Catalog Manager/Simple CRUD maintenance): In the Windows Containers fork, implement and add a client ASP.NET WebForms application (running as a Windows Container) consuming the same microservices, as an example of "lift and shift" scenario.