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
- All projects deleted
Hello, from the appwrite console last week I re-activated some of my old project and published them, yesterday I checked and none of the apps were working, now ...
- Authentication on custom Websocket Serve...
Hi, I want to use a custom Websocket Server (using Bun) for my application. However I cant really figure out authentication on custom servers. Session cookies ...
- Realtime: Listener not triggered on upda...
I self host appwrite 1.8.1. The genereal functionallity works fine. But my realtime subscription isn't updating. I see "Received heartbeat response from realtim...