To multitenancy or not... that is the question 💀
I have an order management application I am currently porting to Laravel and using Filament as the app. Currently I have users assigned to customer_ids
The app will be a monthly fee and usage based. So what guides your decision on multitenancy? I see customers now just having one account tied to one customer. But in the future 🎇 I could see warehouses being invited to manage multiple customers.
3 Replies
A simple example of multitenancy is users belonging to multiple teams, and each team managing different resources. Sounds similar to what you want to do.
Yes I think it is similar. The docs mentioned some potential negatives about multi-tenancy. What are the negatives? Unless I misread it as negatives when it was just explaining that their are some bigger concepts???
Curious on how to limit tenancy management though. I think just having 1 customer be a tenant would be good. And it would be useful if another user could invite a different user to their tenant? Not sure if that makes sense...
I can't think of anything negative about multi-tenancy, if that's what you need. Maybe the docs emphasize that you may not need it, in certain cases. For example, if you just need users and groups, tenancy can be overkill.