Building multi-tenant solutions on AWS

Inspired by the work of the SASS factory team of AWS.

Transcript

1. Building multi-tenant solutions on AWS Rumesh Hapuarachchi @rehrumesh
2. Single Tenant vs Multi Tenant Single Tenant – A single instance of the software and supporting infrastructure serve a single customer. Multi Tenant - A single instance of software runs on a server(s) and serves multiple tenants.
3. Partitioning vs Isolation
4. Isolation Strategies Silo Pooled
5. Silo Isolation
7. Pooled Isolation
8. Things to note ▹ How do you isolate shared resources ▹ Don’t rely on well behaved code ▸ Imagine a nested query
9. Runtime policies
10. Resource Isolation Let's dive deep
11. Silo - Compute Isolation
12. Pooled IAM policy requires a broader scope
13. Pooling with EC2 & lambda
14. Pooled - Containers </3
15. Storage Isolation
16. Isolation & Data partitioning
17. Isolation with S3
18. What about other storage services?
19. Silo Pros 1. Coarse grained Isolation 2. Customer Acceptance 3. Tool alignment Cons 1. Deployment 2. Cost 3. Manageability 4. Account limits Pros 1. Fine grained isolation 2. Resource pooling 3. Agility 4. Cost effective 5. Manageability Cons 1. Customer Acceptance 2. Mix of technologies 3. Account limits Pooled
20. Reference Point
21. rehrumesh rumeshh@99x.lk