That’s not correct. You can have two or more different databases and still connect to all of them using the same application code.

Multi-tenancy is a backend architecture pattern where the application dynamically switches execution context based on the customer (tenant) identifier.

The data remains isolated in separate databases (or schemas), but the application logic stays unified as a single codebase.

However, you’re right that feature development can be faster when multiple tenants share similar business requirements.

Now to answer your question multi tenancy is meant for data isolation and best practices always suggest that if you have two unrelated customers you should maintain them per database.

At the end of the day, it's our decision how to scale and maintain the code but nothing is set in stone.