Skip to content

Update best-practices.md #1

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
shaiwuan wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Update best-practices.md #1

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions best-practices.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -24,4 +24,5 @@ subcollection: databases-for-mysql
| Use connection pooling in the application end. | Pooling reuses connections, avoiding maxing out of connections. Ensure that your pool size is well below the database's `max_connections`. Implement retry logic and catch exceptions to handle pool exhaustion or connection failures.|
| Reduce blast radius by using a dedicated ICD-MySQL instance per production application. | Separation of applications lowers the volume per service instance, minimizing issues caused by aggregation of demand from many applications. |
| Deploy a MySQL read replica per MySQL instance. | Read replicas offer the ability to support read traffic off the main instance, reducing the overall workload, and enhancing reliability.|
| Hosting MySQL on a dedicated instance | For production environments, particularly those anticipating growth, increased traffic, or requiring high reliability and performance, we strongly recommend hosting MySQL on a dedicated instance. This ensures better resource isolation, scalability, and overall system stability. |
{: caption="Best practices" caption-side="top"}