Halfway multi tenancy
Instead of doing true multi-tenancy, this is an immediate solution that will allow us to have multiple instances sharing much of the infrastructure, without fully duplicated instances.
Stanford is doing this to support two additional instances.
-
Stanford Continuing Medical Education - we plan to put up paid courses for the CME program, requiring a separate registration flow and separate class lists. Do not want intermingling of accounts.
-
Carnegie Institution for Science - has nothing to do with CMU. They need separate branding.
Goals
- Ability to support different themes
- Data segregation
- Done with what we have now
- Course separation
- Account separation
Non-Goals
- Different code bases -- we want to install the same code to all instances
- Shared everything
- Full isolation
Note the additions for CME are in blue, Carnegie in red.
-
Shared Studio? No, too weird, and "view live" gets exciting.
-
Redirects between instances? Hope not.
Jarv: why not just run separate silos (new cloudformation runs)?
Summary
-
Split frontends - OK
-
Shared databases with different instances -- fine, don't just separate instances, separate accounts as well
-
Shared memcache but with prefix key -- fine
-
Rabbit / celery - virtual hosts, OK
-
Separate workers - OK
-
Separate heroku - OK