What is data mesh and data fabric advisory?
Data mesh and data fabric advisory helps an organisation decide whether decentralised domain ownership, shared data-product practices, metadata-led integration capabilities, or a combination of these approaches fits its business and technology context. The engagement can assess readiness, define operating and architecture principles, establish governance and decision rights, and create a prioritised adoption roadmap.
What is the difference between data mesh and data fabric?
Data mesh is primarily an organisational and operating-model approach built around domain ownership, data as a product, self-service platform capabilities and federated governance. Data fabric is primarily an architecture and integration approach that uses shared metadata, connectivity, governance, quality and delivery capabilities across distributed data. They solve different parts of the problem and can be used together.
Can data mesh and data fabric be combined?
Yes. A combined model can use domain ownership and product accountability from data mesh while using fabric capabilities for discovery, metadata, lineage, integration, policy, quality and governed access. The right combination depends on business domains, current platforms, operating maturity, control requirements and the problems the organisation is trying to solve.
How do we know whether data mesh is suitable for our organisation?
Suitability should be assessed rather than assumed. Useful evidence includes the clarity of business domains, willingness and capability of domains to own data products, strength of governance, self-service platform maturity, engineering skills, metadata and quality practices, funding model, cross-domain dependencies and the scale of existing central delivery bottlenecks.
What deliverables can we expect from the advisory engagement?
Depending on scope, outputs can include a current-state and readiness assessment, mesh-versus-fabric fit recommendation, domain and data-product map, target operating model, decision-rights model, federated governance principles, target architecture direction, platform capability requirements, risk and dependency register, prioritised initiatives, pilot recommendations and an executive roadmap.
What information should we prepare before the engagement?
Useful starting material includes business priorities, organisation and domain structures, current architecture diagrams, source and platform inventories, metadata and lineage information, governance policies, quality findings, security and privacy requirements, active transformation programmes, data-product or analytics backlogs, known delivery bottlenecks and access to accountable business and technology stakeholders.
Does this service require a specific cloud or data platform?
No. The advisory is requirements-led and can work with existing or planned cloud, lakehouse, warehouse, catalogue, integration, orchestration, data-quality, identity, policy, observability, analytics and AI tooling. Platform recommendations are shaped by confirmed use cases, architecture constraints, control requirements, skills and investment choices rather than by assuming a single vendor.
How are governance, privacy, security and risk handled?
The engagement can define decision rights, ownership, policy guardrails, data classifications, access principles, quality expectations, metadata and lineage requirements, retention and residency considerations, assurance evidence and escalation paths. It supports governance and control design but does not replace legal advice, statutory audit, formal certification or specialist security testing unless those activities are separately commissioned.
Will DataConsultant implement the data mesh or data fabric after the advisory work?
Implementation can be scoped separately. Follow-on work may include architecture definition, data-product design, platform enablement, integration design, governance implementation, metadata and lineage capability, delivery assurance, mobilisation and knowledge transfer. Responsibilities, acceptance criteria and dependencies should be agreed before implementation starts.
How long does a data mesh and data fabric advisory engagement take?
The timeline is confirmed after scoping. It depends on the number of business domains and stakeholders, architecture complexity, evidence availability, maturity of governance and metadata, platform diversity, workshop and review cycles, geographic or regulatory considerations, and whether detailed operating-model, architecture or mobilisation work is included.
How is pricing calculated?
DataConsultant does not publish a fixed fee for this service. Pricing is custom and is confirmed after discovery based on the decisions required, number of domains and stakeholders, assessment depth, architecture and platform complexity, governance and control requirements, workshops, deliverables, onsite needs, implementation support and the level of documentation and executive facilitation required.
Can DataConsultant work with our internal teams and existing vendors?
Yes. The engagement can work alongside business-domain leaders, data offices, architecture, engineering, governance, risk, security and platform teams as well as systems integrators and software vendors. Ownership, evidence access, decision rights, dependencies and escalation routes should be made explicit during mobilisation.
What is not automatically included in the advisory scope?
Software licensing, full platform implementation, large-scale data migration, production data-product build, managed operations, legal advice, statutory audit, penetration testing, regulatory certification and guaranteed business outcomes are not automatically included. Any of these can only be addressed when they are explicitly scoped and supported by the appropriate delivery or specialist capability.
