We are currently architected a 4-10 year blueprint for the data and analytics domain.
We are looking to implement data mesh principles with distributed domain governance. It also includes moving away from centralised data warehouse and data lake.
This appears to be a significant change (it isn't so much as the next step of formalising many previous architectural trends in the department). Stakeholders would like to know if data mesh architecture has been set up or is in the process of being adopted in any other department?
In summary, considering Data Mesh architecture and would like to identify existing case studies we can refer to (as well as any lessons learnt we can leverage)
Bryce, I am also interested in understanding how data mesh has been implemented in other government agencies. If you end up getting any information, please share.
Will do Ty. As an update, as we explore the architecture frameworks, we are heading towards a more hybrid approach. We have some maturity in data lakes/hubs with elements of centralisation. We want to leverage these areas of maturity while onboarding domains/business areas faster and more easily. The decentralisation of governance is a big driver as well. However, general capability in data and analytics outside certain areas is low, so the move to domain-driven data products and decentralised governance will be tempered by the need to uplift aps capabilities across the board. So the immediate to mid-term will be hybrid with a trend towards data mesh frameworks. A journey rather than a sprint. That said, we are also looking at federated analytics and zero etl concepts too.
HelpAbout usContact usPrivacy noticeTerms and conditions
The Data and Digital Professions acknowledge the traditional owners and custodians of country throughout Australia and acknowledges their continuing connection to land, waters and community. We pay our respects to the people, the cultures and the elders past, present and emerging.