Public/system-design-101
1
0
Fork 0
mirror of https://github.com/ByteByteGoHq/system-design-101.git synced 2026-04-01 16:57:23 -04:00
Code Issues Packages Projects Releases Wiki Activity

Made grammatical changes (#10)

Browse Source 
Changed "Separate functional teams need to speak the same language The
dedicated functional teams are only responsible for their own components
and services. " to "Separate functional teams need to speak the same
language and the dedicated functional teams are only responsible for
their own components and services. "

Also changed "Microservices increase system complexity We have separate
services to serve different functions of the system." to "Microservices
increase system complexity and we have separate services to serve
different functions of the system."

#36 - Relevant Issue
This commit is contained in:
Dallin Christensen
2023-10-25 17:48:16 -06:00
committed by GitHub
parent 9734b76131
commit 75f473ec3d
1 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
README.md
View File

@@ -312,11 +312,11 @@ The diagram below shows the differences between code-first development and API-f
</p>
- Microservices increase system complexity We have separate services to serve different functions of the system. While this kind of architecture facilitates decoupling and segregation of duty, we need to handle the various communications among services.
- Microservices increase system complexity and we have separate services to serve different functions of the system. While this kind of architecture facilitates decoupling and segregation of duty, we need to handle the various communications among services.
It is better to think through the system's complexity before writing the code and carefully defining the boundaries of the services.
- Separate functional teams need to speak the same language The dedicated functional teams are only responsible for their own components and services. It is recommended that the organization speak the same language via API design.
- Separate functional teams need to speak the same language and the dedicated functional teams are only responsible for their own components and services. It is recommended that the organization speak the same language via API design.
We can mock requests and responses to validate the API design before writing code.