Appwrite Horizontal Scaling

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!

TL;DR

Developers are looking to scale Appwrite horizontally across multiple nodes and regions for improved traffic handling, reduced latency, and better availability. They're considering using Docker Swarm for replication, but are cautious about potential issues. They plan to use a distributed database and centralized storage. Solution: Consider using Docker Swarm for replication, but be cautious of potential issues with the appwrite-executor container. Implement a distributed database (MongoDB Atlas or Azure CosmosDB) and centralized S3-compatible storage for improved scalability.

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.