Documenting code, one commit at a time.
On the landing project, which serves as a core platform for our users, we recently embarked on a significant architectural evolution. The goal was to seamlessly integrate B2B (business) multi-tenant support alongside our established B2C (personal) model, without compromising backward compatibility for existing users.
When managing multi-tenant applications, ensuring data integrity across all tenants is crucial. Recently, while working on the Reimpact/platform, we encountered an issue during tenant migrations related to non-nullable columns. Here’s how we addressed it.
In a multi-tenant architecture, each tenant often has its own database schema. During migrations, these schemas need to be
When developing multi-tenant applications with Laravel, managing database schema updates across tenants can be tricky. This post discusses how to address a common issue: ensuring that all tenant databases have the necessary schema changes after migrations.
In a multi-tenant Laravel application, each tenant typically has its own database schema.
