Microsoft Fabric and Azure data platforms in Bruges: architecture, capacity and cost

A Fabric capacity bought before anyone has profiled the workloads is an expense in search of a benefit. That is the position several Bruges organisations find themselves in when they call us.

This page is about building a data platform for an organisation in Bruges, Microsoft Fabric, Azure Synapse, Data Factory and the lakehouse patterns underneath them, with the local economy taken seriously. Bruges's base in tourism, hospitality and events, ports, terminals and maritime, and food and drink manufacturing determines the data volumes, the latency requirements and the retention obligations, and those three things decide the architecture. The client population here is shaped by one of Europe's most visited heritage cities and the port of Zeebrugge with vehicle and gas terminals.

Does a Bruges organisation actually need Fabric?

The case for Fabric gets strong when more than one of these holds: import models under strain, the same data needed through both SQL and notebooks, governed self-service for several teams, retention that a desktop model cannot carry, or a Premium capacity already on the bill. One analyst maintaining three import models that refresh in twenty minutes does not need a capacity, and buying one will not improve anything.

What the data actually looks like in Bruges

Ports, terminals and maritime

Vessel, container and yard movement data at very high event volume, with berth planning and customs status driving operational decisions hour by hour. Source systems typically include terminal operating system, vessel traffic systems, customs and single-window platforms, crane and equipment telemetry and ERP.

For a platform design, the consequence is specific. Equipment telemetry and the terminal operating system disagree on what counts as a move, so productivity figures vary by source. So the architecture has to make the raw grain replayable rather than aggregating at ingestion, and the first serving model should be a movement and dwell model joining terminal operations to customs status, which exposes whether delays are operational or regulatory.

Food and drink manufacturing

Short shelf life, high SKU churn, promotional volatility and retailer scorecards that measure you on their definitions rather than yours. Internal service levels read green while the retailer scorecard reads amber, because the two measure different events.

Systems to plan for: ERP, MES, warehouse management, retailer EDI and scorecards and quality systems. HACCP and traceability obligations mean batch records must be retrievable quickly enough to support a withdrawal within hours.

Logistics and freight

Event data from scanners, telematics, EDI and transport management systems, each with its own timestamp semantics and time zone handling. Subcontracted volume arrives as spreadsheets, so a third of the network is effectively unmeasured exactly where control is weakest. Drivers' hours records, customs declarations and posting documentation all carry retention obligations and are frequently requested in audit.

A medallion layout for a ports, terminals and maritime business

The medallion pattern is not complicated, and it is routinely implemented badly: a bronze layer that has already lost fidelity, a silver layer with no testable rules, and a gold layer that is really just the silver layer with different names. Here is how we would lay it out for a Bruges client in ports, terminals and maritime.

Capacity sizing and what it really costs

Fabric capacity is billed by capacity unit. An F2 is roughly US$0.36 per hour pay-as-you-go, about US$260 a month, with around 40 per cent off for a one-year reservation. An F64, the smallest SKU at which report consumers no longer need an individual Pro licence, is roughly US$8,400 a month pay-as-you-go or around US$5,000 reserved.

The arithmetic that matters: F64 only becomes cheaper than per-user licensing somewhere in the region of 350 to 600 readers, depending on the discount you actually pay and whether you reserve capacity. Below that, Pro or PPU per user is normally the right answer, and buying capacity for prestige is a straightforward waste of money.

Capacity is sized from measurement, not from a spreadsheet. Each workload is profiled for its compute shape, for background refresh against interactive query, for concurrency and for when the peaks actually fall, then the result is checked on a trial capacity running your own data. The output is a sizing model that states expected utilisation at launch, at double the readers, and the specific point at which you would need the next SKU. Always price from the current Microsoft rate card for your region and agreement. Any figure in an article older than a quarter should be treated as an order of magnitude, not a quote.

Direct Lake, import or DirectQuery

Direct Lake reads Delta files in OneLake with no import refresh and no DirectQuery round trip, but unsupported constructs trigger fallback and performance then depends on the SQL endpoint. We test it against an import model on your own data and choose on the measured result. In practice Direct Lake tends to win on large, frequently landing tables, which ports, terminals and maritime workloads often are, while import still wins on smaller models with heavy DAX.

Migrating from what you have now

Few Bruges organisations start from nothing. The realistic options are a serving-layer-first adoption, where Fabric takes the gold layer and reporting while existing engineering stays in place, or a domain-by-domain migration with the old platform retained until each domain is validated. Both avoid a big-bang cutover, which is the pattern that produces the rollbacks we get called in to repair. The reference pipeline we build first is usually the system that hurts most, which here is normally terminal operating system.

Residency, latency and the Belgium question

Most Belgian deployments land in West Europe, which is physically in the Netherlands, or in France Central. Microsoft has announced a Belgian datacentre region, so check current availability before committing to an architecture that assumes in-country residency, and in the meantime document the EU-but-not-Belgian position for your data protection officer.

For Bruges specifically, West Europe (Netherlands) is the normal primary with France Central (Paris) as the pair. Latency from Bruges to that region is not usually a constraint for analytical workloads; the constraints that bite are feature availability per region and the processor chain your data protection officer will ask about.

• Belgium's federal structure means some reporting obligations sit with the regions (Flanders, Wallonia and Brussels) rather than nationally, which multiplies the datasets a single organisation must produce.
• Language legislation affects employee-facing systems: reporting used in employment contexts may need to be available in the language of the region where staff are employed.
• As the host of the EU institutions, Brussels has an unusual concentration of organisations working to EU-level reporting rules ahead of national implementation.

Where to go next

If you are weighing a platform decision for a Bruges organisation, a workload assessment will answer it with evidence in two to three weeks, and the written recommendation is yours whatever you decide. Book a technical review.

We work across Belgium and deliver into neighbouring markets regularly. Nearby pages worth reading if your group has sites elsewhere: Ostend, Roeselare, Mouscron, Verviers, Antwerp and Liège.

Frequently asked questions