Modern data platform
Choosing the main platform — Microsoft Fabric, Databricks, Snowflake, or a deliberate mix — that the next five years of data work will build on.
1 user storyOpen
Domain
Data
The data platform decisions — which engine to bet on, Microsoft Fabric, Databricks, or Snowflake — and the storage and governance underneath. Conversations here are usually about consolidating data sprawl, retiring an old data warehouse, or making the numbers trustworthy.
Everyday sub-domains
The standard conversations most organisations have within this domain.
Data warehouse modernisation
Retiring older data warehouses — Synapse dedicated pools, Teradata, Netezza — onto a cloud-native pattern.
1 user storyOpen
Operational databases
Refreshing the day-to-day databases that run customer-facing systems — onto Azure SQL, Cosmos DB, or a deliberate mix of database types for different jobs.
1 user storyOpen
Data integration and pipelines
The plumbing that moves data from where it's created to where it's used — scheduled jobs, real-time change capture, Microsoft Fabric pipelines, Logic Apps.
1 user storyOpen
Specialised sub-domains
Where the conversation needs custom adaptations — regulated, hybrid, or high-stakes.
Lakehouse with Databricks
When the right answer is an open lakehouse design with Databricks Unity Catalog as the governance layer — usually because the customer has a serious machine-learning programme.
1 user storyOpen
Real-time and event-driven data
Streaming data, Kafka, real-time analytics — for the conversations where overnight batch jobs are too slow.
1 user storyOpen