Out app currently is backed by an RDBMS using a column on each table to represent the Tenant-Id.
So each of our customers accesses the same App, which uses WHERE clauses to filter the tenant data.
Can you give me some advice on how this architecture could be implemented in Tigergraph?
For instance: the TenantId should be a property of each Vertex? Or there is a way to use the tenantId to create partitions and subsequently more performant the access.