Skip to content
Sohentix

Architecture Standards

The workspace, capacity and naming rules a Microsoft Fabric platform must satisfy before any item is created in it.

Principle

Processing and reporting never share a workspace.

A runaway notebook, a refresh storm or a badly bounded pipeline should degrade engineering throughput and nothing else. Business reporting sits behind its own boundary so it stays available while the platform is being worked on.

Structure

Processing

PROJ-IngestPROJ-TransformPROJ-Lakehouse

Reporting

PROJ-SemanticModelPROJ-Reports

Platform

PROJ-SharedPROJ-Ops

Workspace separation by function, repeated per environment.

Procedure

  1. 01

    Fix the domain and naming scheme

    Every workspace, item and branch derives its name from a single project code — PROJ — plus function and environment. Placeholder body copy to be completed.

  2. 02

    Split processing from reporting

    Assign separate workspaces for ingestion and transformation versus semantic models and reports. Placeholder body copy to be completed.

  3. 03

    Bound the capacity

    Decide what runs on which capacity, and what is allowed to burst. Placeholder body copy to be completed.

  4. 04

    Record the topology as a written standard

    The layout is documented before it is built, and reviewed when it changes. Placeholder body copy to be completed.

Verification

  • Every workspace name resolves to a function and an environment.
  • No reporting artefact shares a workspace with a processing artefact.
  • Capacity assignment is documented for each workspace.
  • The standard is stored in the repository, not in a chat thread.