jSnake🐍🕊Original post
Rank 2: Process
I'm curious about the performance and scaling implications of having many databases as opposed to having many collections with fewer databases or finally the fewest database and collections with documents isolated by an id attribute.
Which complicates horizontal scaling more? Having thousands of databases or thousands of collections inside a single database or finally the fewest databases and collections with a very large number of documents isolated by an id attribute?
The isolated groups of data will have very few dependencies between each other in my project and I want to make heavy use of the real time API.
Summary
The user is asking about how Appwrite differentiates between collections in different databases. They are also curious about how the Appwrite database is isolated in MariaDB. The team suggests building the database around real-time functionality. Each collection in Appwrite translates to a table in MariaDB. The user is asking about the performance and scaling implications of having many databases versus many collections within a single database, or having fewer databases and collections with documents isolated by an ID attribute. They mention that the isolated groups of data in their project have very few dependencies and they want to make heavy use of the real-time API. No solution is provided in the thread.