Introduction

Welcome to the project 🚀

This platform is built with:

• Laravel
• PHP-FPM
• High concurrency, production traffic

Our primary goal is production stability:

• No Out Of Memory (OOM)
• No long-running requests
• Predictable performance under load

---

Core Rule (Read This First)

Web requests must be fast, bounded, and predictable.

• 120 seconds is a hard safety cap, not a design target
• Most web requests should finish in < 10–15 seconds
• If something cannot meet this, it must be moved to a queue job

---

📘 Onboarding Guide (Read in Order)

Follow these pages in sequence to understand how the system works and how to write safe code:

🧠 System Understanding

• 👉 Architecture
  How requests flow, how PHP-FPM works, and why memory matters

---

⚡ Performance Expectations

• 👉 Performance & SLA
  What “good performance” means for users and APIs

• 👉 Request Limits
  Hard server-enforced limits (timeouts, memory caps)

---

🚫 Rules & Anti-Patterns

• 👉 Forbidden Patterns
  Things that are strictly not allowed in production code

---

✅ Correct Design Patterns

• 👉 Queues & Jobs
  How and when to move heavy work to background jobs

• 👉 Database Rules
  Safe querying patterns to avoid memory explosions

• 👉 Uploads & Payloads
  Handling large files and requests correctly

• 👉 Caching & Cloudflare
  Reducing PHP load using caching and edge behavior

---

🧯 Real Incidents & Enforcement

• 👉 Incident: OOM Case Study
  A real production failure and what we learned from it

• 👉 Code Review Checklist
  Mandatory checklist used to approve or reject PRs

---

Final Reminder

If a feature cannot safely run within web request limits,
it does not belong in an HTTP request.

When in doubt:

• Ask before implementing heavy logic
• Prefer queues
• Prefer simplicity over cleverness

Welcome aboard — build fast, but keep production alive 🚀