The framework for AI era
The framework for AI era
Deployment architectures
13 ways to run API Maker, from the simplest to the most dynamic. Each one uses only API Maker, your databases, MongoDB and Redis, on plain VPS from any provider or on your own servers. No managed cloud services, no lock-in.
Level 1
One or two servers. Live in minutes, every feature included.
Level 2
Separate tiers and a proper release flow, ready to add servers.
Level 3
Several API servers, real-time events everywhere, many customers.
Level 4
Clusters and replicas: no single server can take you down.
Level 5
Servers on several continents and clouds, near every user.
What each architecture gives you. They combine too: a multi-tenant platform can also be highly available and global.
| Architecture | Servers | Databases on their own servers | Add servers for more capacity | Survives the loss of a server | Several clouds or data centers | Serves users from near them | A database per customer or project | Capacity |
|---|---|---|---|---|---|---|---|---|
| 01 All-in-one server | 1 VPS | No | No | No | No | No | No | ~2,759 req/s on 4 cores |
| 02 Separate database server | 2+ VPS | Yes | No | No | No | No | No | ~2,759 req/s on 4 cores |
| 03 Dedicated data tier | 4 VPS | Yes | No | No | No | No | No | ~2,759 req/s on 4 cores |
| 04 Environments with Git | 4+ environments | Yes | Yes | No | No | No | No | ~5,518 req/s on PROD, 2 × 4 cores |
| 05 Load-balanced API servers | 7+ VPS | Yes | Yes | No | No | No | No | ~13,587 req/s on 3 × 8 cores |
| 06 Real-time events across servers | 5+ VPS | Yes | Yes | No | No | No | No | ~8,277 req/s on 3 × 4 cores |
| 07 Many projects, one platform | 5+ VPS | Yes | Yes | No | No | No | Yes | ~7,288 req/s on 2 × 6 cores, shared |
| 08 Multi-tenant: a database per customer | 5+ VPS | Yes | Yes | No | No | No | Yes | ~5,518 req/s on 2 × 4 cores, shared |
| 09 Clustered Redis and databases | 13+ VPS | Yes | Yes | No | No | No | No | ~8,277 req/s on 3 × 4 cores |
| 10 High availability | 10+ VPS | Yes | Yes | Yes | No | No | No | ~8,277 req/s on 3 × 4 cores |
| 11 Multi-cloud | 12+ VPS | Yes | Yes | Yes | Yes | No | No | ~11,036 req/s on 4 × 4 cores |
| 12 Geo-routing: the nearest region | 10+ VPS | Yes | Yes | Yes | Yes | Yes | No | ~8,277 req/s on 3 regions × 4 cores |
| 13 Global enterprise platform | 25+ VPS | Yes | Yes | Yes | Yes | Yes | Yes | ~16,554 req/s on 6 × 4 cores |
Capacity is estimated from our benchmark on Linode shared VPS (MongoDB 6, 10 rows of 10 columns): 788 req/s on 1 core and 4,529 req/s on 8 cores. Your numbers depend on your APIs, your data and your databases.
Moving from one to the next is a matter of servers and connection strings, never of rewriting APIs.
Every server of every architecture is installed the same way, on a plain Ubuntu VPS.
APIs, schemas and settings live in API Maker's MongoDB, so every server serves all of them.
Cache, WebSocket subscriptions, events between servers and locks of the schedulers go through Redis.
Pull on one server and every server of the environment serves the new version, in about 15 seconds.
passJWT, passDBEncryptDecrypt and passCommunication are the same on every server of a project.
Traffic, latency, logs and Docker of every server in one place, with remote restarts.
Pick the situation that sounds like yours.
Tell us about your traffic, your users and your data. We will help you pick and size your architecture.