Database Mesh

Database mesh is a concept developed by 张亮， who wrote this paper on infoq.cn. The main point is about governing data content that is distributed across many instances of databases. The idea is a derived from Service mesh.

Sharding-JDBC

The notion of Database mesh has everything to do with data sharding. The relevant document can be found here: Manual of sharding-JDBC.

Data mesh

There is an article on What is Data mesh?.

There are three important aspects of data mesh:

1. Data Source
2. Data Infrastructure
3. Domain-oriented Data Pipeline

Making Decisions about adopting Data Mesh

The Data Mesh: Re-Thinking Data Integration

These are the five questions you must ask your self to make decisions about adopting Data mesh:

1. Do your operational data owners, data engineers and data consumers struggle to collaborate effectively?
2. Do they struggle to understand one another?
3. Is a lack of business domain knowledge a primary productivity barrier for your data engineers?
4. Is it a primary productivity barrier for your data consumers?
5. Do you have unavoidable, business domain-specific variations in data across regions, BUs, etc.?