Configuration
Database
Architecture
Last updated
3 years ago.
SAAS are usually designed to scale horizontally in terms of client count. What is the point of using a database per clients?
What I suggest is using one database for main app, and one for all clients apps.
To directly respond to your questions:
-
Use migrations (example path: migration/clientside) to create each client database. When upgrading you jsut have to run migrate on each client database to upgrade your system. Subscription upgrade should be handled in your app without change to the database.
-
Answered in 1 with the migration trick.
-
No experience about that sorry.
Last updated
3 years ago.
Sign in to participate in this thread!
Laravel
Laravel News
Laracasts
Laravel Podcast