Database Mesh 2.0: Database Governance in a Cloud Native Environment

This page summarizes the projects mentioned and recommended in the original post on dev.to

Our great sponsors
  • WorkOS - The modern identity platform for B2B SaaS
  • InfluxDB - Power Real-Time Data Analytics at Scale
  • SaaSHub - Software Alternatives and Reviews
  • database-mesh

  • The Database Mesh official website has been launched. The corresponding specification definition is open sourced on this Github repository. The community holds an online discussion every two weeks:

  • conduit

    Ultralight, security-first service mesh for Kubernetes. Main repo for Linkerd 2.x.

  • In 2016, the first generation of Service Mesh was introduced to the public by Linkerd. In 2017, the second generation of Service Mesh, was born thanks to Istio. Its design separates the control plane from data plane, and key behavioral factors such as traffic governance, access control and observability in service governance are abstracted and standardized. Then the application container and governance container are decoupled by Kubernetes’ Sidecar model. It was at this point that Service Mesh was finally shaped.

  • WorkOS

    The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.

    WorkOS logo
  • kubernetes

    Production-Grade Container Scheduling and Management

  • In 2016, the first generation of Service Mesh was introduced to the public by Linkerd. In 2017, the second generation of Service Mesh, was born thanks to Istio. Its design separates the control plane from data plane, and key behavioral factors such as traffic governance, access control and observability in service governance are abstracted and standardized. Then the application container and governance container are decoupled by Kubernetes’ Sidecar model. It was at this point that Service Mesh was finally shaped.

  • istio

    Connect, secure, control, and observe services.

  • In 2016, the first generation of Service Mesh was introduced to the public by Linkerd. In 2017, the second generation of Service Mesh, was born thanks to Istio. Its design separates the control plane from data plane, and key behavioral factors such as traffic governance, access control and observability in service governance are abstracted and standardized. Then the application container and governance container are decoupled by Kubernetes’ Sidecar model. It was at this point that Service Mesh was finally shaped.

  • chaos-mesh

    A Chaos Engineering Platform for Kubernetes.

  • In March 2018, an article titled Service Mesh is the broad trend, what about Database Mesh?, was pubslished on InfoQ China and went viral in the technical community. In this article, Zhang Liang, the founder of Apache ShardingSphere, described Database Mesh concept along with the idea of Service Mesh. Four years later, the Database Mesh concept has been integrated by several companies together with their own tools and ecosystems. Today, in addition to Service Mesh, a variety of “X Mesh” concepts such as ChaosMesh, EventMesh, IOMesh have emerged. Following four years of development, Database Mesh has also started a new chapter: Database Mesh 2.0.

  • InfluxDB

    Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.

    InfluxDB logo
NOTE: The number of mentions on this list indicates mentions on common posts plus user suggested alternatives. Hence, a higher number means a more popular project.

Suggest a related project

Related posts