
Jacops · Construction & infrastructure
Some tenders need a new entity. We can't build a data platform from scratch for each one
A new entity already runs on a data platform of its own, built on the Jacops foundation
Capacity sizing, lakehouse architecture, pipeline patterns, naming conventions. The decisions that determine whether Fabric pays back its bill, made once across dozens of rollouts so you don't make them again. Plus a free accelerator that turns eight questions into Terraform, CI/CD, and a compliance doc.
BEFORE WE START
What teams already running, or considering, Fabric tell us before any work starts. Each one has a way out, and the rest of this page is how we get there.
How we approach it
Capacity without a use case is just a bill. Fabric pays off when you migrate one real workload end-to-end, not when you announce the rollout.
How we approach it
Fabric only gets you closer to a single source of truth if there's an actual semantic layer between your data and your reports. Otherwise it's the old setup with a new logo.
How we approach it
Heavy ETL and interactive queries fighting on one capacity is a recipe for unpredictable performance. The fix is usually splitting capacities and turning on Autoscale Billing for Spark, not buying a bigger SKU.
How we approach it
Naming sounds boring until your environment has 40 workspaces and 200 lakehouses. By then, ad-hoc names are a permanent tax on everyone who touches the platform.
Six of the patterns we apply on every Fabric rollout. Written down so you can read them before talking to us.
Strict workload isolation for compliance and billing. Avoids noisy-neighbour performance issues between heavy ETL and interactive users. Pairs with Autoscale Billing for Spark on F-SKUs, billed separately from the base capacity.
Medallion architecture mapped to Landing/Staging, ADS, and Gold business products. Delta for all transactional tables. Parquet only where archival doesn't need ACID. OneLake shortcuts to share curated tables across lakehouses without copying.
F4-F8 for dev. F16-F32 for small to medium prod. F64 for enterprise. Sized for peak concurrency and 6-12 month growth, not for average load. Avoid mixing heavy ETL and interactive queries on the same capacity.
MERGE upserts over blind inserts. Save watermarks before state changes, not after. Deterministic keys so replays are safe. Retries with exponential backoff, circuit breakers for dependent jobs, structured logging at every step.
Workspace folders don't survive Git promotion. Naming does. We standardise on patterns like LH_STORE_Sales_Silver and DP_ORCHS_NightlyETL. Environment lives in the workspace scope and deployment pipeline, never in the artifact name.
VS Code as the primary dev environment with Fabric extensions. OneLake Explorer for file-level operations and offline sync. SSMS for SQL deep-dives. Power BI Desktop with PBIP files for version-controlled semantic models.
Four steps. The same every time. The decisions inside each one come from doing it dozens of times, not from reading a docs page.
One real workload, one person who cares about the answer. Not a tenant-wide migration plan. The thing we ship in the first iteration must be useful on its own.
We measure actual data volume, query patterns, and refresh cadence before we size capacity. A wrong F-SKU is the most expensive Fabric mistake we see.
Source to OneLake to semantic model to Power BI. Medallion structure, MERGE-based pipelines, standardised naming, separated capacities for ETL vs interactive. The patterns we apply on every rollout.
Domain structure, admin runbooks, capacity monitoring, documentation. Your team runs it without us, and the next workload reuses what's already built.
We turned our rollout patterns into a tool. Answer eight questions, get Terraform, CI/CD pipelines, a compliance justification doc, and an interactive rollout explorer back. Use it as a starting point, or hand it to us to deliver.
Our AI-driven migration framework scans your estate, designs the Fabric target mapped to medallion layers, and generates deployable pipelines, SQL, and notebooks. AI-assisted, never autonomous: our engineers sign off at every gate.

Jacops · Construction & infrastructure
A new entity already runs on a data platform of its own, built on the Jacops foundation
Practical write-ups from our Fabric projects: deployment, CI/CD, and what agents change.
Strategy decides if Fabric is the right pick. We build it. Experts keep it running once we hand it over.
From business questions to a data, AI and software direction your organisation can follow.
Explore →Data and analytics, AI, and custom software. Built with adoption and ownership from day one.
Explore →Specialists who think like teammates. Keep your engine running and your team growing.
Explore →Half-hour call. We'll tell you if it's the right pick for your situation, and what it actually takes to get one workload running well.
Book a Fabric chatEager to join our team? View open positions