API Maker

Low Memory Footprint

API Maker process takes around ~140MB, (including all native code) so we have lots of memory available on server of 1GB RAM, to do amazing tasks.
API Maker internally doing lazy loading of modules, so if the project is using only MySQL, it will not load drivers of other databases. So it can operate on low memory.
API Maker provides high performance with advanced features stream APIs which are capable of getting a huge amount of data from the database.

So, if we want to get 10GB of data from database servers, API Maker’s server having 1GB RAM can easily do it.
While doing that it will not block any other operations and API calls.
We will not see any spike in memory usage because it will get data in small chunks from the database server and send it to the user.
Streaming APIs and file operations, are very useful in long-running schedulers and data migration tasks, or sending many emails to users.
As you can see in the above image, API Maker runs on small memory footprint and a single server can handle many components.
They all together can handle ~700+ Req/s and ~2.5M+ Req/hour, which is ~25% of total UPI transactions of August 2022 in India which is ~9.1M Req/hour. API Maker benchmark payload is benchmark_dataset.json, and Linode VPS 1vCPU 1GB RAM server.