Theme:
- Single vs Multi Tenant
Scenario based questions:
-
You have a backend service + database that is accessed by a tenant's id However some of this data needs to be provided to the frontend without exposing that id. This data on the frontend is need for bootstrapping some of the frontend services. How would you address this task?
-
Client has a need to publish articles using a 3rd party API that allows you to build an article and provide content to it. The cavet is in order to build an article you have to make a sequential request to the API to first create the article category, section and finally the body with the content. What would use? How could you scale so that client could publish many articles at once?
-
Client needs to onboard new customers. During the discovery phase they notice that are multiple business domains that are affected by the onboarding process. So now the question becomes what pattern can we use here, we can build a centralized service that maintains any and all domains logic that pertains to the onboarding phase or we can leave it to the business domains to coordinate and build services that expose APIs and other entities that will be operated during onboarding.