From e8e512f85af6f0bcc7bcb2748924d089eaa7bd55 Mon Sep 17 00:00:00 2001
From: Shaiwuan Sims <44821759+shaiwuan@users.noreply.github.com>
Date: Wed, 3 Dec 2025 14:24:52 -0500
Subject: [PATCH] Update best-practices.md

Added best practice explaining why and a when a user should consider to host their mysql on dedicated instance.

reference content needed task :

https://watson.service-now.com/now/cwf/agent/record/sn_customerservice_task/580754da475132504fc04c4a516d438a
---
 best-practices.md | 1 +
 1 file changed, 1 insertion(+)

diff --git a/best-practices.md b/best-practices.md
index 17c1f57..4efe63d 100644
--- a/best-practices.md
+++ b/best-practices.md
@@ -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"}