[SOLVED] Multi Appwrite instances or one?

hi, i love Appwrite idea,

i have a question, so, i will be definitely self-hosting the app, but i have a question.

i will be building very heavy traffic web apps that would contain like millions of documents.

so, is it better to have a different instance of Appwrite for each heavy app or have them all in one application.

i am just looking for maintainability and continuity.

if i went to one single instance approach, is there a way to limit or increase resources for a specific project ?

and all those projects will be hosted in just a single mariadb instance and not multiple ones?

thanks!

TL;DR

The user is asking whether it is better to have separate instances of Appwrite for each heavy app or one instance for all of them. They also inquire if it is possible to limit or increase resources for a specific project and if all projects will be hosted in a single MariaDB instance. The response suggests that for high availability, it's best to have one Appwrite instance for each platform. However, for development purposes, using only one instance that holds all projects is sufficient. It is not possible to limit resources for a specific project. When scaling, it is recommended to have a dedicated cluster for the database.

Appwrite was designed to be 1 instance w/ multiple projects. Up to you on scaling, though.

No, you can't limit resources for a particular project.

1 instance of Appwrite = 1 database instance. When scaling, though, it is best to have a dedicated cluster for your database.

If you really would like to use Appwrite to the backend for several heavily used platforms then at this stage I think it's more optimal to run multiple instances, one for each platform. Some part of Appwrite isn't scalable efficiently

Thank you both for answering the question.

I will go with the second approach (appwrite instance for each platform) as high availability for each platform is required for me.