Merge pull request dotnet#10610 from dotnet-architecture/docker-lifecycle/04.6-soa-applications

Containerized Docker Application Lifecycle - 04.6

Author: mvelosop

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

@@ -3,16 +3,18 @@ title: SOA applications
 description: Bear in mind that containers can also be a useful deployment option for SOA applications.
 author: CESARDELATORRE
 ms.author: wiwagn
-ms.date: 11/23/2018
+ms.date: 02/15/2019
 ---
-# SOA applications
+# Service-oriented applications
 
-SOA was an overused term and meant so many different things to different people. But at a minimum and as a common denominator, SOA, or service orientation, mean that you structure the architecture of your application by decomposing it in multiple services (most commonly as HTTP services) that can be classified in different types like subsystems or, in other cases, as tiers.
+Service-Oriented Architecture (SOA) was an overused term that meant many different things to different people. But as a common denominator, SOA means that you structure the architecture of your application by decomposing it into several services (most commonly as HTTP services) that can be classified in different types like subsystems or, in other cases, as tiers.
 
-Today, you can deploy those services as Docker containers, which solves deployment-related issues because all of the dependencies are included within the container image. However, when you need to scale-out SOAs, you might encounter challenges if you are deploying based on single instances. This is where a Docker clustering software or orchestrator will help you. We'll look at this in greater detail in the next section when we examine microservices approaches.
+Today, you can deploy those services as Docker containers, which solve deployment-related issues because all of the dependencies are included in the container image. However, when you need to scale out SOAs, you might encounter challenges if you are deploying based on single instances. This challenge can be handled using Docker clustering software or an orchestrator. We'll look at orchestrators in greater detail in the next section, when we explore microservices approaches.
 
-At the end of the day, the container clustering solutions are useful for both a traditional SOA architecture or for a more advanced microservices architecture in which each microservice owns its data model. And, thanks to multiple databases, you also can scale-out the data tier instead of working with monolithic databases shared by the SOA services. However, the discussion about splitting the data is purely about architecture and design.
+Docker containers are useful (but not required) for both traditional service-oriented architectures and the more advanced microservices architectures.
+
+At the end of the day, the container clustering solutions are useful for both a traditional SOA architecture and for a more advanced microservices architecture in which each microservice owns its data model. And thanks to multiple databases, you also can scale out the data tier instead of working with monolithic databases shared by the SOA services. However, the discussion about splitting the data is purely about architecture and design.
 
 >[!div class="step-by-step"]
 >[Previous](state-and-data-in-docker-applications.md)
->[Next](orchestrate-high-scalability-availability.md)
+>[Next](orchestrate-high-scalability-availability.md)