From 3043ea9e0599417fd055e9d3b87c2fb9b4874aaa Mon Sep 17 00:00:00 2001 From: Sander Holvoet Date: Fri, 12 Feb 2021 01:10:42 +0100 Subject: [PATCH] Fix docker-compose.yml reference (#22793) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Fixes #22656 🛠️ --- .../database-server-container.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/architecture/microservices/multi-container-microservice-net-applications/database-server-container.md b/docs/architecture/microservices/multi-container-microservice-net-applications/database-server-container.md index 179f7937f8ba0..2f92e3c694b3d 100644 --- a/docs/architecture/microservices/multi-container-microservice-net-applications/database-server-container.md +++ b/docs/architecture/microservices/multi-container-microservice-net-applications/database-server-container.md @@ -9,7 +9,7 @@ You can have your databases (SQL Server, PostgreSQL, MySQL, etc.) on regular sta ## SQL Server running as a container with a microservice-related database -In eShopOnContainers, there's a container named `sqldata`, as defined in the [docker-compose.yml](https://github.com/dotnet-architecture/eShopOnContainers/blob/master/docker-compose.yml) file, that runs a SQL Server for Linux instance with the SQL databases for all microservices that need one. +In eShopOnContainers, there's a container named `sqldata`, as defined in the [docker-compose.yml](https://github.com/dotnet-architecture/eShopOnContainers/blob/main/src/docker-compose.yml) file, that runs a SQL Server for Linux instance with the SQL databases for all microservices that need one. A key point in microservices is that each microservice owns its related data, so it should have its own database. However, the databases can be anywhere. In this case, they are all in the same container to keep Docker memory requirements as low as possible. Keep in mind that this is a good-enough solution for development and, perhaps, testing but not for production.