You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+12-9Lines changed: 12 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -14,11 +14,15 @@ Sample .NET Core reference application, powered by Microsoft, based on a simplif
14
14
**Architecture overview**: This reference application is cross-platform either at the server and client side, thanks to .NET Core services capable of running on Linux or Windows containers depending on your Docker host, and to Xamarin for mobile apps running on Android, iOS or Windows/UWP plus any browser for the client web apps.
15
15
The architecture proposes a simplified microservice oriented architecture implementation with multiple autonomous microservices (each one owning its own data/db) and implementing different approaches within each microservice (simple CRUD vs. DDD/CQRS patterns) using Http as the current communication protocol.
16
16
<p>
17
-
The plan is to add asynchronous communication for data updates propagation across multiple services based on integration events and an event bus plus other features defined at the <ahref='https://github.com/dotnet/eShopOnContainers/wiki/01.-Roadmap-and-Milestones-for-future-releases'>roadmap</a>.
17
+
It also supports asynchronous communication for data updates propagation across multiple services based on Integration Events and an Event Bus plus other features defined at the <ahref='https://github.com/dotnet/eShopOnContainers/wiki/01.-Roadmap-and-Milestones-for-future-releases'>roadmap</a>.
The microservices are different in type, meaning different internal architecture patterns approaches depending on it purpose, as shown in the image below.
Additional miroservice styles with other frameworks and No-SQL databases will be added, eventually. This is a great opportunity for pull requests from the community, like a new microservice using Nancy, or even other languages like Node, Go, Python or data containers with MongoDB with Azure DocDB compatibility, PostgreSQL, RavenDB, Event Store, MySql, etc. You name it! :)
24
28
@@ -30,15 +34,14 @@ Additional miroservice styles with other frameworks and No-SQL databases will be
30
34
## Related documentation and guidance
31
35
While developing this reference application, we are creating a reference Guide/eBook named <b>"Architecting and Developing Containerized and Microservice based .NET Applications"</b> which explains in detail how to develop this kind of architectural style (microservices, Docker containers, Domain-Driven Design for certain microservices) plus other simpler architectural styles, like monolithic apps that can also live as Docker containers.
32
36
<p>
33
-
There's also an additional eBook focusing on Containers/Docker lifecycle (DevOps, CI/CD, etc.) with Microsoft Tools, already published.
34
-
You can start reviewing these Guides/eBooks here:
37
+
There are also additional eBooks focusing on Containers/Docker lifecycle (DevOps, CI/CD, etc.) with Microsoft Tools, already published plus an additional eBook focusing on Enterprise Apps Patterns with Xamarin.Forms.
38
+
You can download them and start reviewing these Guides/eBooks here:
| <ahref='docs/architecting-and-developing-containerized-and-microservice-based-net-applications-ebook-early-draft.pdf'>**Download** (Early DRAFT, still work in progress)</a> | <ahref='https://aka.ms/dockerlifecycleebook'>**Download**- First Edition from late 2016</a> |
| <sup> <ahref='https://aka.ms/microservicesebook'>**Download** (Early DRAFT, still work in progress)</a> </sup> | <sup> <ahref='https://aka.ms/dockerlifecycleebook'>**Download**(First Edition from late 2016) </a> </sup> | <sup> <ahref='https://aka.ms/xamarinpatternsebook'>**Download** (Early DRAFT, still work in progress) </a> </sup> |
42
45
43
46
Send feedback to [cesardl@microsoft.com](cesardl@microsoft.com)
44
47
<p>
@@ -89,7 +92,7 @@ The app was also partially tested on "Docker for Mac" using a development MacOS
89
92
90
93
## Sending feedback and pull requests
91
94
As mentioned, we'd appreciate to your feedback, improvements and ideas.
92
-
You can create new issues at the issues section, do pull requests and/or send emails to eshop_feedback@service.microsoft.com
95
+
You can create new issues at the issues section, do pull requests and/or send emails to **eshop_feedback@service.microsoft.com**
93
96
94
97
## Questions
95
98
[QUESTION] Answer +1 if the solution is working for you (Through VS2017 or CLI environment):
- ExternalCatalogBaseUrl=http://${ESHOP_PROD_EXTERNAL_DNS_NAME_OR_IP}:5101 #Local: You need to open your host's firewall at range 5100-5105. at range 5100-5105.
- identityUrl=http://identity.api:5105 #Local: You need to open your host's firewall at range 5100-5105. at range 5100-5105.
53
+
- BasketUrl=http://basket.api:5103
54
+
- EventBusConnection=rabbitmq
51
55
ports:
52
56
- "5102:5102"
53
57
@@ -82,10 +86,13 @@ services:
82
86
83
87
webstatus:
84
88
environment:
85
-
- ASPNETCORE_ENVIRONMENT=Development
89
+
- ASPNETCORE_ENVIRONMENT=Production
90
+
- ASPNETCORE_URLS=http://0.0.0.0:5107
86
91
- CatalogUrl=http://catalog.api:5101/hc
87
92
- OrderingUrl=http://ordering.api:5102/hc
88
93
- BasketUrl=http://basket.api:5103/hc
89
-
- IdentityUrl=http://10.0.75.1:5105/hc
94
+
- mvc=http://webmvc:5100/hc
95
+
- spa=http://webspa:5104/hc
96
+
- IdentityUrl=http://${ESHOP_PROD_EXTERNAL_DNS_NAME_OR_IP}:5105 #Local: Use ${ESHOP_PROD_EXTERNAL_DNS_NAME_OR_IP}, if using external IP or DNS name from browser.
0 commit comments