Skip to content

Commit e63833d

Browse files
mvelosopBillWagner
authored andcommitted
Cross updating with Microservices eBook v2.1.02 - Chapter 1 (#7414)
* Cross updating with eBook v2.1.02 * Fix revision date * Add cover caption * Include @mairaw comments
1 parent dbbeae9 commit e63833d

File tree

3 files changed

+76
-49
lines changed

3 files changed

+76
-49
lines changed

docs/standard/microservices-architecture/index.md

Lines changed: 76 additions & 49 deletions
Original file line numberDiff line numberDiff line change
@@ -3,40 +3,82 @@ title: .NET Microservices. Architecture for Containerized .NET Applications
33
description: .NET Microservices Architecture for Containerized .NET Applications | Microservices are modular and independently deployable services. Docker containers (for Linux and Windows) simplify deployment and testing by bundling a service and its dependencies into a single unit, which is then run in an isolated environment.
44
author: CESARDELATORRE
55
ms.author: wiwagn
6-
ms.date: 06/06/2018
6+
ms.date: 08/31/2018
77
---
88

9-
![](./media/cover.png)
9+
# .NET Microservices: Architecture for Containerized .NET Applications
10+
![Book cover](./media/cover-small.png)
1011

11-
# .NET Microservices. Architecture for Containerized .NET Applications
12+
**EDITION v2.1.02** - Updated to ASP.NET Core 2.1
1213

13-
DOWNLOAD available at: <https://aka.ms/microservicesebook>
14+
This guide is an introduction to developing microservices-based applications and managing them using containers. It discusses architectural design and implementation approaches using .NET Core and Docker containers.
1415

15-
PUBLISHED BY
16+
To make it easier to get started, the guide focuses on a reference containerized and microservice-based application that you can explore. The reference application is available at the [eShopOnContainers](https://github.com/dotnet-architecture/eShopOnContainers) GitHub repo.
1617

17-
Microsoft Developer Division, .NET and Visual Studio product teams
18+
## Action links
1819

19-
A division of Microsoft Corporation
20+
* Download this eBook in your format of choice: | [PDF](https://aka.ms/microservicesebook) | [MOBI](https://www.microsoft.com/net/download/thank-you/microservices-architecture-ebook-mobi) | [EPUB](https://www.microsoft.com/net/download/thank-you/microservices-architecture-ebook-epub) |
2021

21-
One Microsoft Way
22+
* Clone/Fork the reference application [eShopOnContainers on GitHub](https://github.com/dotnet-architecture/eShopOnContainers)
23+
24+
* Watch the [introductory video on Channel 9](http://aka.ms/microservices-video)
2225

23-
Redmond, Washington 98052-6399
26+
* Get to know the [Microservices Architecture](http://aka.ms/MicroservicesArchitecture) right away
2427

25-
Copyright © 2018 by Microsoft Corporation
28+
## Introduction
2629

27-
All rights reserved. No part of the contents of this book may be reproduced or transmitted in any form or by any means without the written permission of the publisher.
30+
Enterprises are increasingly realizing cost savings, solving deployment problems, and improving DevOps and production operations by using containers. Microsoft has been releasing container innovations for Windows and Linux by creating products like Azure Container Service and Azure Service Fabric, and by partnering with industry leaders like Docker, Mesosphere, and Kubernetes. These products deliver container solutions that help companies build and deploy applications at cloud speed and scale, whatever their choice of platform or tools.
2831

29-
This book is provided “as-is” and expresses the author’s views and opinions. The views, opinions and information expressed in this book, including URL and other Internet website references, may change without notice.
32+
Docker is becoming the de facto standard in the container industry, supported by the most significant vendors in the Windows and Linux ecosystems. (Microsoft is one of the main cloud vendors supporting Docker.) In the future, Docker will probably be ubiquitous in any datacenter in the cloud or on-premises.
3033

31-
Some examples depicted herein are provided for illustration only and are fictitious. No real association or connection is intended or should be inferred.
34+
In addition, the [microservices](https://martinfowler.com/articles/microservices.html) architecture is emerging as an important approach for distributed mission-critical applications. In a microservice-based architecture, the application is built on a collection of services that can be developed, tested, deployed, and versioned independently.
3235

33-
Microsoft and the trademarks listed at http://www.microsoft.com on the “Trademarks” webpage are trademarks of the Microsoft group of companies.
36+
## About this guide
3437

35-
Mac and macOS are trademarks of Apple Inc.
38+
This guide is an introduction to developing microservices-based applications and managing them using containers. It discusses architectural design and implementation approaches using .NET Core and Docker containers. To make it easier to get started with containers and microservices, the guide focuses on a reference containerized and microservice-based application that you can explore. The sample application is available at the [eShopOnContainers](https://github.com/dotnet-architecture/eShopOnContainers) GitHub repo.
3639

37-
The Docker whale logo is a registered trademark of Docker, Inc. Used by permission.
40+
This guide provides foundational development and architectural guidance primarily at a development environment level with a focus on two technologies: Docker and .NET Core. Our intention is that you read this guide when thinking about your application design without focusing on the infrastructure (cloud or on-premises) of your production environment. You will make decisions about your infrastructure later, when you create your production-ready applications. Therefore, this guide is intended to be infrastructure agnostic and more development-environment-centric.
3841

39-
All other marks and logos are property of their respective owners.
42+
After you have studied this guide, your next step would be to learn about production-ready microservices on Microsoft Azure.
43+
44+
## Version
45+
46+
This guide has been revised to cover **.NET Core 2.1** version plus many additional updates related to the same “wave” of technologies (that is. Azure and additional 3rd party technologies) coinciding in time with .NET Core 2.1. That’s why the book version has also been updated to version **2.1**.
47+
48+
## What this guide does not cover
49+
50+
This guide does not focus on the application lifecycle, DevOps, CI/CD pipelines, or team work. The complementary guide [Containerized Docker Application Lifecycle with Microsoft Platform and Tools](https://aka.ms/dockerlifecycleebook) focuses on that subject. The current guide also does not provide implementation details on Azure infrastructure, such as information on specific orchestrators.
51+
52+
### Additional resources
53+
54+
- **Containerized Docker Application Lifecycle with Microsoft Platform and Tools** (downloadable e-book)
55+
[*https://aka.ms/dockerlifecycleebook*](https://aka.ms/dockerlifecycleebook)
56+
57+
## Who should use this guide
58+
59+
We wrote this guide for developers and solution architects who are new to Docker-based application development and to microservices-based architecture. This guide is for you if you want to learn how to architect, design, and implement proof-of-concept applications with Microsoft development technologies (with special focus on .NET Core) and with Docker containers.
60+
61+
You will also find this guide useful if you are a technical decision maker, such as an enterprise architect, who wants an architecture and technology overview before you decide on what approach to select for new and modern distributed applications.
62+
63+
### How to use this guide
64+
65+
The first part of this guide introduces Docker containers, discusses how to choose between .NET Core and the .NET Framework as a development framework, and provides an overview of microservices. This content is for architects and technical decision makers who want an overview but don't need to focus on code implementation details.
66+
67+
The second part of the guide starts with the [Development process for Docker based applications](#ch_dev_process_for_docker_based_apps) section. It focuses on development and microservice patterns for implementing applications using .NET Core and Docker. This section will be of most interest to developers and architects who want to focus on code and on patterns and implementation details.
68+
69+
## Related microservice and container-based reference application: eShopOnContainers
70+
71+
The eShopOnContainers application is an open-source reference app for .NET Core and microservices that is designed to be deployed using Docker containers. The application consists of multiple subsystems, including several e-store UI front ends (a Web MVC app, a Web SPA, and a native mobile app). It also includes the back-end microservices and containers for all required server-side operations.
72+
73+
The purpose of the application is to showcase architectural patterns. **IT IS NOT A PRODUCTION-READY TEMPLATE** to start real-world applications. In fact, the application is in a permanent beta state, as it’s also used to test new potentially interesting technologies as they show up.
74+
75+
## Send us your feedback!
76+
77+
We wrote this guide to help you understand the architecture of containerized applications and microservices in .NET. The guide and related reference application will be evolving, so we welcome your feedback! If you have comments about how this guide can be improved, please send them to:
78+
79+
80+
81+
## Credits
4082

4183
Co-Authors:
4284

@@ -97,55 +139,40 @@ Participants and reviewers:
97139
> **Michael Friis**, Product Manager, Docker Inc
98140
>
99141
> **Charles Lowell**, Software Engineer, VS CAT team, Microsoft
142+
>
143+
> **Miguel Veloso**, Sr. Consultant at Turing Challenge
100144
101-
## Introduction
102-
103-
Enterprises are increasingly realizing cost savings, solving deployment problems, and improving DevOps and production operations by using containers. Microsoft has been releasing container innovations for Windows and Linux by creating products like Azure Container Service and Azure Service Fabric, and by partnering with industry leaders like Docker, Mesosphere, and Kubernetes. These products deliver container solutions that help companies build and deploy applications at cloud speed and scale, whatever their choice of platform or tools.
104-
105-
Docker is becoming the de facto standard in the container industry, supported by the most significant vendors in the Windows and Linux ecosystems. (Microsoft is one of the main cloud vendors supporting Docker.) In the future, Docker will probably be ubiquitous in any datacenter in the cloud or on-premises.
106-
107-
In addition, the [microservices](https://martinfowler.com/articles/microservices.html) architecture is emerging as an important approach for distributed mission-critical applications. In a microservice-based architecture, the application is built on a collection of services that can be developed, tested, deployed, and versioned independently.
108-
109-
## About this guide
110-
111-
This guide is an introduction to developing microservices-based applications and managing them using containers. It discusses architectural design and implementation approaches using .NET Core and Docker containers. To make it easier to get started with containers and microservices, the guide focuses on a reference containerized and microservice-based application that you can explore. The sample application is available at the [eShopOnContainers](https://github.com/dotnet-architecture/eShopOnContainers) GitHub repo.
112-
113-
This guide provides foundational development and architectural guidance primarily at a development environment level with a focus on two technologies: Docker and .NET Core. Our intention is that you read this guide when thinking about your application design without focusing on the infrastructure (cloud or on-premises) of your production environment. You will make decisions about your infrastructure later, when you create your production-ready applications. Therefore, this guide is intended to be infrastructure agnostic and more development-environment-centric.
114-
115-
After you have studied this guide, your next step would be to learn about production-ready microservices on Microsoft Azure.
116145

117-
## What this guide does not cover
146+
## Copyright
118147

119-
This guide does not focus on the application lifecycle, DevOps, CI/CD pipelines, or team work. The complementary guide [Containerized Docker Application Lifecycle with Microsoft Platform and Tools](https://aka.ms/dockerlifecycleebook) focuses on that subject. The current guide also does not provide implementation details on Azure infrastructure, such as information on specific orchestrators.
148+
DOWNLOAD available at: <https://aka.ms/microservicesebook>
120149

121-
### Additional resources
150+
PUBLISHED BY
122151

123-
- **Containerized Docker Application Lifecycle with Microsoft Platform and Tools** (downloadable e-book)
124-
[*https://aka.ms/dockerlifecycleebook*](https://aka.ms/dockerlifecycleebook)
152+
Microsoft Developer Division, .NET and Visual Studio product teams
125153

126-
## Who should use this guide
154+
A division of Microsoft Corporation
127155

128-
We wrote this guide for developers and solution architects who are new to Docker-based application development and to microservices-based architecture. This guide is for you if you want to learn how to architect, design, and implement proof-of-concept applications with Microsoft development technologies (with special focus on .NET Core) and with Docker containers.
156+
One Microsoft Way
129157

130-
You will also find this guide useful if you are a technical decision maker, such as an enterprise architect, who wants an architecture and technology overview before you decide on what approach to select for new and modern distributed applications.
158+
Redmond, Washington 98052-6399
131159

132-
### How to use this guide
160+
Copyright © 2018 by Microsoft Corporation
133161

134-
The first part of this guide introduces Docker containers, discusses how to choose between .NET Core and the .NET Framework as a development framework, and provides an overview of microservices. This content is for architects and technical decision makers who want an overview but who do not need to focus on code implementation details.
162+
All rights reserved. No part of the contents of this book may be reproduced or transmitted in any form or by any means without the written permission of the publisher.
135163

136-
The second part of the guide starts with the [Development process for Docker based applications](#ch_dev_process_for_docker_based_apps) section. It focuses on development and microservice patterns for implementing applications using .NET Core and Docker. This section will be of most interest to developers and architects who want to focus on code and on patterns and implementation details.
164+
This book is provided “as-is” and expresses the author’s views and opinions. The views, opinions and information expressed in this book, including URL and other Internet website references, may change without notice.
137165

138-
## Related microservice and container-based reference application: eShopOnContainers
166+
Some examples depicted herein are provided for illustration only and are fictitious. No real association or connection is intended or should be inferred.
139167

140-
The eShopOnContainers application is a reference app for .NET Core and microservices that is designed to be deployed using Docker containers. The application consists of multiple subsystems, including several e-store UI front ends (a Web app and a native mobile app). It also includes the back-end microservices and containers for all required server-side operations.
168+
Microsoft and the trademarks listed at http://www.microsoft.com on the “Trademarks” webpage are trademarks of the Microsoft group of companies.
141169

142-
This microservice and container-based application source code is open source and available at the [eShopOnContainers](https://aka.ms/MicroservicesArchitecture) GitHub repo.
170+
Mac and macOS are trademarks of Apple Inc.
143171

144-
## Send us your feedback!
172+
The Docker whale logo is a registered trademark of Docker, Inc. Used by permission.
145173

146-
We wrote this guide to help you understand the architecture of containerized applications and microservices in .NET. The guide and related reference application will be evolving, so we welcome your feedback! If you have comments about how this guide can be improved, please send them to:
174+
All other marks and logos are property of their respective owners.
147175

148-
149176

150177
>[!div class="step-by-step"]
151178
[Next](container-docker-introduction/index.md)
79.8 KB
Loading
32.1 KB
Loading

0 commit comments

Comments
 (0)