I'm going to start a SAAS model web application and gone through many searches. Finally in my mind have few queries. So I'm posting here to get experts ideas to overcome these problems before starts.
-
How to handle situations like upgrade/change subscription in future?
-
If I use separate database for each tenant, then while I want to update a small feature means I have to update it in each and every database/codebase. This is so difficult?
-
I heard about module based schema/database with tables for SAAS apps. Is it good to use that kind of schema for SAAS web apps?
Expecting your valuable suggestions/ideas for the above queries.
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.
Sign in to participate in this thread!
Laravel
Laravel News
Laracasts
Laravel Podcast