Hi!! I’m planning to scale Appwrite horizontally and I wanted to ask if there are any updates or best practices in 2026 for doing this in multi-node or multi-region setups.
I’ve been considering using Docker Swarm to handle the replication of stateless containers (API, workers, realtime), but I understand there are some limitations like the appwrite-executor container that keeps the function state in memory, so replicating it can cause issues.
My idea would be to have a distributed database (MongoDB Atlas or Azure CosmosDB) so all nodes have access to the same data, and a centralized S3-compatible storage so all nodes share the same files.
I’d love to get advice on the best way to scale Appwrite horizontally today, how to handle Docker Swarm and the executor to avoid issues with functions, or any other robust alternatives you could recommend. Thanks everyone!
Hey, I am curious, why do you need horizontal scaling?
Also, FYI appwrite does not use mongodb nor cosmosdb.
I want to scale Appwrite horizontally across multiple nodes and regions to handle more traffic, reduce latency by connecting users to the closest server, and improve availability if a node goes down.
True. But i think that Rds mysql (Or rds for mariaDb) could work
I see. I just asked cause that's usually only needed by big projects usually. I can't help much myself.
cc @Aditya Oberai Hopefully can help
Thanks!
Recommended threads
- OAuth provider credentials reverting [CR...
Hi team, I’m experiencing repeated OAuth configuration resets in my Appwrite project. ## Issue 1 – Google OAuth credentials reverting * I configure my own Goog...
- Hey everyone! I'm trying to self-host th...
Hey everyone! I'm trying to self-host the latest Appwrite version (1.8.1) on Coolify. Which docker-compose.yml file should I use from their repo? Can someone he...
- Weird CLI error
I'm a little lost ``` appwrite init project --organization-id my_actual_organiztion_id --project-name "test" --project-id "unique_id" ℹ Info: For detailed erro...