API Maker
The backend engine for the AI era
Every nightEpisode 80 6:52 10 chapters November 2026
Back up MongoDB, PostgreSQL, MySQL, MariaDB, SQL Server and Oracle on schedules into Amazon S3, Cloudflare R2, Backblaze B2 or any store which speaks S3 from the API Maker admin panel: encrypted, kept by your rules, and restored table by table.
In the playlists The complete course Migrations & tenants Run in production
Here is Automatic Backup. Your databases are backed up on schedules, into an S3 bucket. The backups are encrypted, kept by your rules, and brought back table by table.
Backups are usually a cron job and a script on one server. The cloud keys are pasted into it. Old files are removed by another script, or never. And nobody ever tried a restore. With API Maker, you make a plan for each database, on the schedule you want. It is made by the own program of the database, and encrypted before it leaves. Old backups are removed by your rules.
And a restore is compared with the database of now, table by table. In this video: an S3 storage, checked, a plan, a backup and its log, a plan for every engine, the bucket, browsed, and a restore, table by table.
On the dashboard, under Operations, open Automatic Backup. It has three tabs: the storages, the plans, and the log. There is no storage yet. Click New storage. Pick the store: Amazon S3, Cloudflare R2, Backblaze B2, Wasabi, DigitalOcean Spaces, Akamai, Scaleway, Google Cloud Storage, MinIO, or any other store that speaks S3, like the one of Calm Home. Give a name, the address of the store, the bucket, and a folder for the backups.
Then give the keys. The secret key is sealed on the server as soon as it is saved, and never shown again. Check lists the bucket, writes a small file, reads it, and removes it, just as a backup does. All four work.
Save it. Open Plans, and click New plan. Name it Catalog every night. For what, pick mongodb, one database, and catalog. The form of the file and its options are the same as in Import and Export. For when, you can pick every few hours, every day, some days of the week, once a month, or a cron expression. Pick every day, at two in the morning, in its time zone.
The dialog says the schedule in words, and shows its next five times. Next, where, and for how long. Pick the store of Calm Home. Each instance and each plan gets its own folder. Grandfather father son keeps the seven newest backups, one a day for a week, one a week for a month, and one a month for a year. That is a year in about twenty five files.
The newest one always stays. Next, security and alerts. Encrypt means the archive is encrypted on the server before it leaves, with the password of the plan, sealed on the server. Gently is on by default, so the backup takes the smallest share of the server. And you can give an address to tell when a backup fails. Slack, Teams, or Discord can take it. Save it.
The plan waits for its time. Back up now runs it at once. The dump is encrypted, and sent into the bucket in parts. The log shows the backup, its size, and how long it took. Its details show the dump, the upload, and the old backups removed, with its key in the bucket, and its SHA-256.
Here is a plan for every engine. MongoDB every night, PostgreSQL every six hours, the orders of MySQL, MariaDB on Sundays, SQL Server, and Oracle once a month. Each one is backed up by the own program of the database. The log keeps every backup, every restore, and every missed time. Every server looks at the plans every twenty seconds. The first server that takes a time runs it. So there is one backup per time, however many servers there are.
If no server was there for a time, it is noted as missed, not run late. And the archive never sits in memory. It goes from the disk to the bucket, piece by piece.
Open Storages, and browse. You see the bucket as it is. There is a folder for each instance, and a folder for each plan. Inside, each backup is an encrypted archive. Its details come from the description saved beside it: the plan, the database, the program, the SHA-256, and each collection with its documents.
Now a restore. Last night, catalog was backed up. This morning, three reviews were deleted by mistake. Here are its backups, newest first. Click Restore, and pick where it goes. It can go into its own database, or into a new one, to look at the backup without touching anything. Click Bring it back. The backup comes from the bucket, it is decrypted, and its SHA-256 is checked. Then it is compared with the database of now.
reviews changed, and the others are the same. Pick nothing, then Replace for reviews. What reviews holds now will go, and the name of the database confirms it. Click Restore. It is counted after, and reviews is ok. The log keeps who restored what.
Encrypt the plans whose data leaves your network, and keep their passwords somewhere else. Give the keys of a storage the smallest rights: list the bucket, then write, read, and remove in its folder. And try a restore now and then, into a new database. It touches nothing.
To sum up. S3 storages are checked before they are used. Plans have a schedule, a time zone, and rules for how long to keep backups. Backups are encrypted, gentle, and send an alert when one fails. Every engine is covered, and every backup is in the log. And a restore is compared, table by table. Next: the API Testing page. API Maker. Build faster, spend smarter, deliver better.
Length 6:28API Testing
Length 10:05Six engines
Length 12:53Analytics
Length 7:03Scale out