Is there a best practice of creating multi tenant application?

Hi, I have question about creating multi tenant application. In order to create multi tenant application, I tried these things: 1. I downloaded 'License Pool Manager' from AppStore , and imported module package into my application . 2. I related 'LicensePool' Entity with all entities of my application. 3. I added "X-path constraint" to each entities such as : 4. I created "before commit event" to all entities, which relate entity to LicensePool entity . Is there any other solution to create multi tenant application? I want to know best practice. Best regards.
1 answers

Creating a multi-tenant application can start with your steps:

  1. Connect all entities to an entity 'tenant'. You can consider connecting not all directly but via another entity
  2. Fill the tenant data in Before commit events
  3. Change the access rules (use path to user).
  4. Access rules on specializations: don't use attributes of the generalization.
  5. Tick 'Apply entity access' on all relevant microflows.
  6. Mind the scheduled events. In some cases you need a special user to run parts of. That is too complex to describe here.
  7. Create conversion microflow in case of an existing assocation
  8. Take care of standard modules like excelimporter. It needs extra attention to make them multitenant. None of the appstore is multi-tenant.
  9. Webservices: connect the webservice user to a tenant as well and give all external parties separate accounts.
  10. Check needed app-engines on the cloud because the database load/queries are heavier

It would need a full blog to describe all steps in detail. This is only a short list.