From 3488275f3553dd3003bc2f4e0d01e51484a7e1c0 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Halil=20=C4=B0brahim=20Kalkan?= Date: Sat, 9 Nov 2024 23:03:30 +0300 Subject: [PATCH] Update guide.md --- docs/en/solution-templates/guide.md | 18 ++++++++++++++++-- 1 file changed, 16 insertions(+), 2 deletions(-) diff --git a/docs/en/solution-templates/guide.md b/docs/en/solution-templates/guide.md index 838af272c2..aaa7dc26ef 100644 --- a/docs/en/solution-templates/guide.md +++ b/docs/en/solution-templates/guide.md @@ -126,7 +126,7 @@ So, both of [single-layer](single-layer-web-application/index.md) and [layered]( In the following conditions, you may consider to build a modular software solution: * If your **domain is too complex** to develop and maintain in a single monolith codebase. -* If your business domain is easy to **split into sub-domains**. +* If your business domain is possible to **split into sub-domains**. * If you have **multiple teams** that will work on the solution. * If you are considering to **migrate** your application to a **microservice system**. @@ -136,4 +136,18 @@ Also, even if you are considering to build a microservice system, most of the ti ### Microservice Solution Template -ABP's [microservice startup template](microservice/index.md) ... \ No newline at end of file +ABP's [microservice startup template](microservice/index.md) includes multiple services, API gateways and applications that are well integrated to each other and ready to be a great **base solution for your microservice system**. Here, is an overall diagram that shows the main components of the solution (they vary based on the options while you are creating your solution): + +![ms-overall-architecture](microservice/images/overall-architecture.png) + +#### When to use the Microservice Solution Template? + +In the following conditions, you may consider to build a microservice system: + +* If your **domain is too complex** to develop and maintain in a single monolith codebase. +* If your business domain is possible to **split into sub-domains**. +* If you have **multiple teams** that will work on the solution in parallel. +* If you need to **develop**, **test**, **deploy** and **scale services** independently. +* If you need to use **multiple technology stacks** (some services can be built with .NET and some others can be built with other technologies). +* If you need to serve **too many users** concurrently with a **high available** and **fault tolerant** system. +* If you have **devops** knowledge and culture in your company. If you can deal with **complex** development, build, test, deployment and production environments. \ No newline at end of file