Veecks
Railway deploy for microservice architecture
Models for a single multi-tenant:
Company: #id, name, ...other company info...
User: #id, name, password, company, user_type
Appointment: #id, datatime, employee, costumer
Services:
AdminPanel: see, edit or delete apointments from costumers
AppointmentManager: allow costumers to create or cancel appointments
So far so simple, but what if a company actually wants appointments to be notified via email everytime they are made?
Then i would need to handle which companies have access to this feature, then i would need to check what is the company configuration, adding more complexity for its model and the necessity of a new email_notifier service.
43 replies
Railway deploy for microservice architecture
For a single multi-tenant app, i d have to handle 3 types of user: Company, CompanyEmployee, CompanyUser
I see your concerns about it.
For each service in this single multi-tenant app, i'd have to handle wich user type i am dealing with and where it belongs. After defining this, i would have to handle if the permission, this would involve:
- is the route for employees?
- is the route for comapny costumers?
- does the company have access to this feature?
This not only makes the data models more complex but also the distribution of responsabilities between the services kinda odd i think.
43 replies