adelorenzo
/
getting-started
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

Merge dbae842f9c into 13386236e4

This commit is contained in:
Gomolemo 2021-06-29 16:30:56 -07:00 committed by GitHub
parent 13386236e4 dbae842f9c
commit 29665db5b2
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
docs/tutorial/multi-container-apps/index.md
View File

@ -4,12 +4,12 @@ application stack. The following question often arises - "Where will MySQL run?
container or run it separately?" In general, **each container should do one thing and do it well.** A few
reasons:
- There's a good chance you'd have to scale APIs and front-ends differently than databases
- Separate containers let you version and update versions in isolation
- There's a good chance you'd have to scale APIs and front-ends differently than databases.
- Separate containers let you version and update versions in isolation.
- While you may use a container for the database locally, you may want to use a managed service
for the database in production. You don't want to ship your database engine with your app then.
- Running multiple processes will require a process manager (the container only starts one process),
which adds complexity to container startup/shutdown
which adds complexity to container startup/shutdown.
And there are more reasons. So, we will update our application to work like this: