om-data-model-design

Design scalable multi-tenant data models by enforcing standard audit columns like organization_id, tenant_id, is_active, created_at, updated_at, and deleted_at on all entities. This ensures consistent tenant isolation and lifecycle tracking across application modules.

Manage database migrations by defining clear module boundaries without cross-module ORM relations. Generate, review, and apply migration paths safely to preserve tenant-scoped data integrity across isolated application components.

Data models use UUID primary keys to guarantee globally unique identifiers across distributed systems and tenant boundaries. This prevents primary key collisions during data aggregation or synchronization across independent modules.

No, you should not define cross-module ORM relationships for tenant-scoped entities. Preserving strict module boundaries prevents tight coupling and ensures that data model modifications remain isolated and safe during migrations.

Creating new entities requires standard columns including id, organization_id, tenant_id, is_active, created_at, updated_at, and deleted_at. These fields enforce tenant isolation and provide consistent soft-deletion and audit tracking.