From de2aa0409c5dae5e354ea915738b3d7634032d96 Mon Sep 17 00:00:00 2001 From: Cesar De la Torre Date: Tue, 10 Oct 2017 17:05:08 -0700 Subject: [PATCH 1/3] Update README.md --- README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index ccf4617e7..7987aa1c6 100644 --- a/README.md +++ b/README.md @@ -14,9 +14,9 @@ To access the .NET Core 1.1 version you can use the `netcore1.1` tag ([https://g > ### DISCLAIMER > **IMPORTANT:** The current state of this sample application is **BETA** for the .NET Core 2.0 version, and v1.0 for the .NET Core 1.1.2 version tagged ([https://github.com/dotnet-architecture/eShopOnContainers/tree/netcore1.1](https://github.com/dotnet-architecture/eShopOnContainers/tree/netcore1.1)) -P> +

> This reference application proposes a simplified microservice oriented architecture implementation to introduce technologies like .NET Core with Docker containers through a comprehensive application. The chosen domain is an eShop/eCommerce but simply because it is a well-know domain by most people/developers. -However, this sample application should not be considered as an "eCommerce reference model", at all. The implemented business domain might not be ideal from an eCommerce business point of view. It is neither trying to solve all the problems in a large, scalable and mission-critical distributed system. It is just a bootstrap for developers to easily get started in the world of Docker containers and microservices with .NET Core. +However, this sample application should not be considered as an "eCommerce reference model", at all. The implemented business domain might not be perfect from an eCommerce business point of view. It is neither trying to solve all the problems in a large, scalable and mission-critical distributed system, like hyper-scale or production-ready security. It is just a bootstrap for developers to easily get started in the world of Docker containers and microservices with .NET Core. >

The next step after understanding Docker containers and microservices development with .NET Core, is to select a microservice cluster/orchestrator like Azure Service Fabric or Kubernetes, DC/OS or Docker Swarm (in Azure Container Service). Kubernetes and Service Fabric are being tested with eShopOnContainer. > Additional steps already tested in eShopOnContainers are about moving your databases to HA cloud services (like Azure SQL DB), to implement your EventBus with Azure Service Bus or any other production ready Service Bus in the market. From 13f86b8911a9e2cb7a49c6dc06c9b243253a919d Mon Sep 17 00:00:00 2001 From: Cesar De la Torre Date: Tue, 10 Oct 2017 17:06:20 -0700 Subject: [PATCH 2/3] Update README.md --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 7987aa1c6..05cc8998f 100644 --- a/README.md +++ b/README.md @@ -14,7 +14,7 @@ To access the .NET Core 1.1 version you can use the `netcore1.1` tag ([https://g > ### DISCLAIMER > **IMPORTANT:** The current state of this sample application is **BETA** for the .NET Core 2.0 version, and v1.0 for the .NET Core 1.1.2 version tagged ([https://github.com/dotnet-architecture/eShopOnContainers/tree/netcore1.1](https://github.com/dotnet-architecture/eShopOnContainers/tree/netcore1.1)) -

+ > This reference application proposes a simplified microservice oriented architecture implementation to introduce technologies like .NET Core with Docker containers through a comprehensive application. The chosen domain is an eShop/eCommerce but simply because it is a well-know domain by most people/developers. However, this sample application should not be considered as an "eCommerce reference model", at all. The implemented business domain might not be perfect from an eCommerce business point of view. It is neither trying to solve all the problems in a large, scalable and mission-critical distributed system, like hyper-scale or production-ready security. It is just a bootstrap for developers to easily get started in the world of Docker containers and microservices with .NET Core. >

The next step after understanding Docker containers and microservices development with .NET Core, is to select a microservice cluster/orchestrator like Azure Service Fabric or Kubernetes, DC/OS or Docker Swarm (in Azure Container Service). Kubernetes and Service Fabric are being tested with eShopOnContainer. From bbec0e33947abb49a6311149f65a25e483bec27a Mon Sep 17 00:00:00 2001 From: Cesar De la Torre Date: Tue, 10 Oct 2017 17:07:15 -0700 Subject: [PATCH 3/3] Update README.md --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 05cc8998f..4e372b0c1 100644 --- a/README.md +++ b/README.md @@ -16,7 +16,7 @@ To access the .NET Core 1.1 version you can use the `netcore1.1` tag ([https://g > **IMPORTANT:** The current state of this sample application is **BETA** for the .NET Core 2.0 version, and v1.0 for the .NET Core 1.1.2 version tagged ([https://github.com/dotnet-architecture/eShopOnContainers/tree/netcore1.1](https://github.com/dotnet-architecture/eShopOnContainers/tree/netcore1.1)) > This reference application proposes a simplified microservice oriented architecture implementation to introduce technologies like .NET Core with Docker containers through a comprehensive application. The chosen domain is an eShop/eCommerce but simply because it is a well-know domain by most people/developers. -However, this sample application should not be considered as an "eCommerce reference model", at all. The implemented business domain might not be perfect from an eCommerce business point of view. It is neither trying to solve all the problems in a large, scalable and mission-critical distributed system, like hyper-scale or production-ready security. It is just a bootstrap for developers to easily get started in the world of Docker containers and microservices with .NET Core. +However, this sample application should not be considered as an "eCommerce reference model", at all. The implemented business domain might not be perfect from an eCommerce business point of view. It is neither trying to solve all the problems in a large, high scalable and mission-critical distributed system, like hyper-scale or production-ready security. It is just a bootstrap for developers to easily get started in the world of Docker containers and microservices architectures with .NET Core. >

The next step after understanding Docker containers and microservices development with .NET Core, is to select a microservice cluster/orchestrator like Azure Service Fabric or Kubernetes, DC/OS or Docker Swarm (in Azure Container Service). Kubernetes and Service Fabric are being tested with eShopOnContainer. > Additional steps already tested in eShopOnContainers are about moving your databases to HA cloud services (like Azure SQL DB), to implement your EventBus with Azure Service Bus or any other production ready Service Bus in the market.