Thierry Delprat
tdelprat@nuxeo.com
https://github.com/tiry/
Generic use case
Multi-tenants application
Multi-tenants Infrastructure
vs
Multi-tenants application
All clients share the same application.
Application manages data & configuration partitionning.
Multi-tenants Infrastructure
vs
Multi-tenants application
All clients share the same application.
Application manages data & configuration partitionning.
Multi-tenants Infrastructure
All clients share the same infrastructure.
Deploy isolated customized application on PaaS.
vs
the classic way
Document Store
Security
Life Cycle
Indexing
Versioning
all clients share the same application
application manages data and configuration partitionning
Logical isolation
Physical isolation
Shallow isolation
Monolithic
Scaling number of tenants adds complexity
Well adapted for lightweight customization.
Easy first step.
Cloud native approach
rely on infrastructure to provide tenants isolation
application does not need to be impacted
Bake custom images
Bake custom images
Bake custom images
Deploy custom images
Deploy custom images
Docker containers !
Leverage AWS infrastructure
Unlimited Customization
Flexibility of isolated deployments
Full security Isolation & Quotas
Build Your Own Application
Infrastructure Cost
Overhead is not that significant
(Docker is lightweight, JVM ~500MB)
Anyway, provisioning automation is needed to scale
(DNS, DB, Backup ...)
Choosing the right approach