This document discusses different database design approaches for software as a service (SaaS) applications with multiple tenants. It begins by introducing the presenter and their interests and background in web development and databases. It then addresses the issue of "noisy neighbors" when all tenants share a single database. The document proceeds to examine three main approaches: 1) having a separate database for each tenant, 2) using a hybrid model with a shared database and microservices, and 3) keeping all tenants on one database. It concludes by thanking the audience and providing contact information.

1. Multi-tenant
Database Design
for SaaS
Võ Duy Tuấn
Founder
Teamcrop.com

2. Vo Duy Tuan
§ PHP, Javascript, Flutter
§ Web Scalability & Optimization
§ Data Mining
§ ERP System
§ Docker & Microservices
Interests
Founder @ Teamcrop.com

3. One BIG Problem…

4. Noisy Neighbors

5. Today, I do not talk about…
• Database Modeling in UML
• Database Replication
• Database Sharding
• Storage Engine
• Query Optimization
• SQL / NoSQL Compare

6. 1. Single-tenant (Stand-alone App)

7. 2.1. One Database for All

8. 2.1. One Database for All

9. 2.2. Each Database per Tenant

10. 2.2. Each Database per Tenant
(cont.)

11. 2.3. Hybrid DB with Microservices

12. 2.3. Hybrid DB with Microservices
(cont.)

13. 2.3. Hybrid DB with Microservices
(cont.)

14. 2.3. Hybrid DB with Microservices
(cont.)

15. Thanks!
CONTACT:
voduytuan@teamcrop.com
bloghoctap.com