This model involves multiple clients, or tenants, sharing cloud resources. It's efficient in resource utilization and cost-effective since infrastructure and application costs are distributed among the users. However, it may offer less customization and could be perceived as less secure due to shared resources.
In this subset of multi-tenancy, tenants share both the application instance and the infrastructure. It maximizes resource efficiency and minimizes costs. The downside is potentially less data isolation and limited customization.
Here, each client has a separate instance of the application and may have dedicated infrastructure. It offers more security, control, and customization, making it suitable for clients with specific compliance needs. However, this comes at a higher cost due to the dedicated resources.
This involves clients managing their own infrastructure, either on-premises or in a private cloud. It provides maximum control, customization, and potentially better security, but requires significant investment in hardware, software, and maintenance.
Each model suits different organizational needs based on factors like budget, control requirements, and compliance considerations.
For larger codebases, we recommend automating this process with a tool like Second. Connect Second to your GitHub account, run a module, and get a pull request! If you need additional help with this migration, whether you are doing it manually or automatically with Second, please connect with one of our migration experts on Discord.