diff --git a/scalability/cold-start-strategy.md b/scalability/cold-start-strategy.md
new file mode 100644
index 0000000..6ac74c9
--- /dev/null
+++ b/scalability/cold-start-strategy.md
@@ -0,0 +1,70 @@
+# Cold Start Strategy for New Containers
+
+## Overview
+
+A cold start occurs when the platform launches a new container because application traffic has increased and additional capacity is required.
+
+## Strategy
+
+### 1. Keep Warm Instances
+
+Maintain a small number of idle containers (2–3 replicas) that are always running and ready to receive traffic immediately.
+
+---
+
+### 2. Horizontal Auto Scaling
+
+Automatically create additional containers when one or more of the following conditions are met:
+
+- CPU usage exceeds 70%
+- Memory usage exceeds 75%
+- Request rate increases significantly
+- Response time exceeds the defined threshold
+
+---
+
+### 3. Fast Container Startup
+
+Reduce container startup time by:
+
+- Using lightweight Docker images
+- Installing only required packages
+- Minimizing application initialization
+- Preloading configuration files
+
+---
+
+### 4. Health Checks
+
+A new container should not receive production traffic until it successfully passes:
+
+- Readiness Probe
+- Health Check
+
+This ensures users are only routed to healthy containers.
+
+---
+
+### 5. Rolling Updates
+
+Deploy new application versions gradually to avoid downtime.
+
+Example:
+
+Old Version
+██████████
+
+↓
+
+New Version
+██░░░░░░░░
+
+↓
+
+████░░░░░
+
+↓
+
+██████████
+
+This strategy guarantees continuous service availability during deployments.
diff --git a/scalability/ghaymah-block-storage.md b/scalability/ghaymah-block-storage.md
new file mode 100644
index 0000000..0e9fe2e
--- /dev/null
+++ b/scalability/ghaymah-block-storage.md
@@ -0,0 +1,63 @@
+# Using Ghaymah Block Storage for Stateful Workloads
+
+## Overview
+
+Ghaymah Block Storage provides persistent storage that remains available even if containers are restarted, replaced, or rescheduled.
+
+It is designed for applications that must preserve data.
+
+## Common Stateful Workloads
+
+- PostgreSQL
+- MySQL
+- MongoDB
+- Elasticsearch
+- Jenkins
+- GitLab
+- File Storage
+- Application Uploads
+
+---
+
+## Benefits
+
+### Persistent Data
+
+Data remains available after:
+
+- Container restart
+- Node failure
+- Deployment updates
+
+---
+
+### High Performance
+
+Block Storage provides low-latency, high-performance storage suitable for databases and transactional workloads.
+
+---
+
+### Easy Scaling
+
+Storage volumes can be expanded without recreating the application.
+
+---
+
+### Reliability
+
+Storage is independent of containers, reducing the risk of data loss and improving application resilience.
+
+---
+
+## Example Architecture
+
+Application Container
+        |
+        |
+Persistent Volume
+        |
+        |
+Ghaymah Block Storage
+        |
+        |
+ PostgreSQL Database