Playlist · 4 videos · 18 min
Migrations, multi-tenant and languages
Database migrations once per environment, one set of APIs with a database per tenant, error messages in every language, and database names masked per account.
The videos of this playlist
6:221. MigrationsDatabase Migrations in TypeScript or Python, Once per Environment
Changes to your databases that run once in every environment, in order, in the language of your team. Write a migration in TypeScript and one in Python, test it first, run the pending scripts from the dialog or from every deploy, and see what each server remembers.
4:372. Multi-tenantMulti-Tenant APIs: One Set of APIs, a Database per Tenant
One set of APIs for every customer, each with a database of its own. Keep tenants in a table named by the secret, build a multi-tenant instance with one structure for many databases, pick the tenant by path or header, refuse suspended tenants, and move a tenant with one call.
3:563. i18nTranslate API Error Messages into Every Language with One Header
Every error of your APIs in the language of the person who called them, without one line of translation in your code. Build a French dictionary, see what a dictionary holds, translate the errors of your own custom APIs, and pick the language with one request header.
3:284. MaskingDatabase Name Masking: One Name in Code, Any Database per Developer
Your code names the production database, while your laptop, your staging server and your teammates have other copies. Database name masking keeps one name in the code and lets each account map it to another database: the same address, every API following the mask, and nothing committed to Git.