From 9662880dbbd736a32a8a419cd9951cc903f22ad4 Mon Sep 17 00:00:00 2001
From: Daniel Sevostyanov <12199206+SevDan@users.noreply.github.com>
Date: Fri, 19 Mar 2021 22:06:19 +0400
Subject: [PATCH] #1 small 5. Scalable... fragment

---
 ...development-and-operations-01-incomplete-000001.txt | 10 ++++++++--
 1 file changed, 8 insertions(+), 2 deletions(-)

diff --git a/common/development/1/mgppqs-1-common-development-and-operations-01-incomplete-000001.txt b/common/development/1/mgppqs-1-common-development-and-operations-01-incomplete-000001.txt
index cdb6ced..41dbde1 100644
--- a/common/development/1/mgppqs-1-common-development-and-operations-01-incomplete-000001.txt
+++ b/common/development/1/mgppqs-1-common-development-and-operations-01-incomplete-000001.txt
@@ -98,7 +98,7 @@ C. Critical Information
 	4.1. Events Driven
 	4.2. Source of Trurh
 	4.3. CQRS
-5. Replication & Reliable Infrastructure
+5. Scalable & Reliable Infrastructure
 
 D. Common Topics
 1. Departments & Intercommunication
@@ -848,7 +848,13 @@ So, it solves some problems (event sourcing storage will be source of truth) wit
 It has some problems with write & reads reordering: some difficult solutions can has race conditions of it.
 So, you should think over all core aspects before implements CQRS. Maybe you cant use it in some cases.
 
-5. Replication & Reliable Infrastructure
+5. Scalable & Reliable Infrastructure
+
+If you develop big product or think that your product will grow up, you should care about scalability.
+Some technologies provides built-in utilities that can help you with logic scaling, but you should care about infrastructure scalability by yourself.
+
+The most important point is thinking about scalability at architecture time, infrastructure is only base.
+You cant build good scalable product without complex approach. 
 
 -- TODO 5. --