Wayne82
commented
9 months ago This is so true. As a cloud application, basically it is really just to help users to store, update and read (and share) their own data in the cloud. And as a multi-tenants system, it is crucial to design the whole system to efficiently narrow down to the portion of the data that are relevant (and authorized) to a user in the context which the user is interacting with the system, either create, update or query. And all the limitations we need to plan ahead is to guarantee such efficiency of user interacting with the system. But, before that (defining the limits), for a service oriented architecture (SOA), all involved services must have a consistent multi-tenants data model, that all have the same way of organizing data, e.g. collections, and collections of collections (tenants), not only for the efficiency of operating on the data, but also setup the security boundary for different users, and prepare for further scalability by sharding, etc. Unfortunately, I don't think some of the services in the system we have worked on together even have a tenant model. Thus, as more users come and use the system, it is quite painfully to scale.
timwiegand
The Ubiquitous Database Grid View
You’re building a full stack application that enables teams of people to do … something. In order to manage the process of doing something, the teams collaborate by creating, filling in, finding, sorting and archiving forms. There will be some industry specific bits of workflow that let you convi...
https://www.thecandidstartup.org/2023/06/12/database-grid-view.html