Blog / System Architecture

System Architecture

Roles, row-level security, multi-tenancy and privacy boundaries — the structural decisions that are expensive to retrofit.

The architecture decisions that matter most are usually the ones about who can see what. A learning platform with students, teachers and parents, or a rental platform with owners, managers and tenants, both collapse into the same problem: many parties over one dataset, each entitled to a different slice of it.

My default is to put that enforcement in the database rather than in application code, attach roles to relationships instead of accounts, and let each audience get a different zoom level over the same events. It keeps a bug in one endpoint from becoming a data leak across the product.

Writing on system architecture (1)

Built in practice

Hire for this

Other topics

← All writing · Work with Fredrick Onyango