---
# System prepended metadata

title: Untitled

---

Aviacommerce Restructuring:

With multitenant:
 - All tenant/wholesaler CRUD would be done on public tenant.
 - Clicking on tenant name would take to that tenant/wholesaler system.

pros: 
1. Easy to handle on codebase level.
2. code will be maintainable.


Without multitenant:

with unique url for each wholeseller
- Without multitenant if the system is queried according to name in url, everything has to be handled manually when appending to query "WHERE tenant = {passed_name}" which would be quite cumbersome and non maintainable.

cons: 
1. everything needs to be handled manually.
2. will be non-maintainable and complex code.


Without unique url:
Actions on development level
1. create table for wholeseller
2. associate user table to wholeseller

- pros: actual multitenancy is not required
- Cons: if employee is associated with more than one wholeseller (case need to handled)