Merge pull request dotnet#10606 from dotnet-architecture/docker-lifecycle/04.2-design-docker-applications

Containerized Docker Application Lifecycle - 04.2

Author: mvelosop

docs/standard/containerized-lifecycle-architecture/design-develop-containerized-apps/design-docker-applications.md

@@ -3,14 +3,16 @@ title: Design Docker applications
 description: Find here a reference to an in-depth guide to microservices architecture, because that's a topic that it's not detailed in this guide.
 author: CESARDELATORRE
 ms.author: wiwagn
-ms.date: 11/23/2018
+ms.date: 02/15/2019
 ---
 # Design Docker applications
 
-Chapter 1 introduced the fundamental concepts regarding containers and Docker. That information is the basic level of information you need to get started. But, enterprise applications can be complex and composed of multiple services instead of a single service or container. For those optional use cases, you need to know additional approaches to design, such as Service-Oriented Architecture (SOA) and the more advanced microservices concepts and container orchestration concepts. The scope of this document is not limited to microservices but to any Docker application life cycle, therefore, it does not explore microservices architecture in depth because you also can use containers and Docker with regular SAO, background tasks or jobs, or even with monolithic application deployment approaches.
+Chapter 1 introduced the fundamental concepts regarding containers and Docker. That information is the basic level of information you need to get started. But, enterprise applications can be complex and composed of multiple services instead of a single service or container. For those optional use cases, you need to know additional approaches to design, such as Service-Oriented Architecture (SOA) and the more advanced microservices concepts and container orchestration concepts. The scope of this document is not limited to microservices but to any Docker application life cycle, therefore, it does not explore microservices architecture in depth because you also can use containers and Docker with regular SOA, background tasks or jobs, or even with monolithic application deployment approaches.
+
+**More info** To learn more about enterprise applications and microservices architecture in depth, read the guide [NET Microservices: Architecture for Containerized .NET Applications](https://docs.microsoft.com/dotnet/standard/microservices-architecture) that you can also download from <https://aka.ms/MicroservicesEbook>.
 
 However, before we get into the application life cycle and DevOps, it is important to know how you are going to design and construct your application and what are your design choices.
 
 >[!div class="step-by-step"]
 >[Previous](index.md)
->[Next](common-container-design-principles.md)
+>[Next](common-container-design-principles.md)