Multi-tenant SaaS architecture on Oracle Cloud

Views in this map

1. 1
   The platformOne region: 140 pooled sponsors, 18 dedicated, and one in a compartment of its own.
2. 2
   Pooled tier140 sponsors share one namespace, database and bucket, kept apart by sponsor ID.
3. 3
   Dedicated tier18 sponsors each get their own namespace, database, bucket and key.
4. 4
   Isolated tenantBrackwater has its own compartment, network and cluster, reached over FastConnect.
5. 5
   OKE clusterOne cluster, three node pools: 140 sponsors in one namespace, 18 in their own.

The platform ‹ › Pooled tier ‹ › Dedicated tier ‹ › Isolated tenant · The platform ▸ OKE cluster

Flows to play

• ▷
  A site saves a visitA pooled sponsor’s site saves a visit: every hop is shared until the sponsor ID picks the rows. In the Pooled tier view.
• ▷
  A sponsor leavesA dedicated sponsor takes its data home, then its key is destroyed, and every copy with it. In the Dedicated tier view.
• ▷
  Brackwater’s own pathA Brackwater site and reviewer reach Brackwater’s stack, and an engineer gets in only with approval. In the Isolated tenant view.

The model behind it

81 records of 19 types. Every box on the map is one of them, so the filters and the record panel read the same data.

• Sponsors 19
• Services 10
• People 6
• Gateways 6
• Subnets 6
• Node pools 4
• Tiers 3
• 12 more types 27

Filters

Tier and Data stored: pick a value and everything else fades.