local/fabric-x-yugabyte.yaml¶

fabric-x-yugabyte.yaml runs the default local container network with the committer storage layer switched from PostgreSQL to YugabyteDB.

Use it when you want to test the committer against YugabyteDB while keeping Fabric CA enrollment, TLS, mTLS, one load generator, and local monitoring.

Network Diagram¶

The diagram below summarizes this inventory's Fabric-X services and how they fit together.

local Fabric-X YugabyteDB inventory

Inventory Details¶

All long-running services run as local containers. The Fabric CA databases still use PostgreSQL containers, while the committer database is a compact YugabyteDB deployment.

This inventory deploys these logical services on the local machine:

5 Fabric CA servers and 5 PostgreSQL databases for Fabric CA state.
4 orderer groups. Each group has 1 router, 1 consenter, 1 assembler, and 1 batcher.
1 committer with validator, verifier, coordinator, sidecar, and query service.
1 YugabyteDB master and 1 YugabyteDB tablet in cluster 1.
1 load generator.
Monitoring with node exporter, Prometheus, and Grafana.

Note

You can scale YugabyteDB for stronger performance by adding more master and tablet hosts. See the distributed Fabric-X inventory for a larger topology with replicated YugabyteDB masters and tablets.

flowchart TD
  all --> network
  network --> fabric_cas
  network --> fabric_x
  all --> load_generators
  all --> monitoring
  fabric_cas --> fabric_ca_servers
  fabric_cas --> fabric_ca_dbs["Fabric CA PostgreSQL DBs"]
  fabric_x --> fabric_x_orderers
  fabric_x --> fabric_x_committer
  fabric_x_orderers --> orderer_groups["fabric_x_orderer_1..4"]
  fabric_x_committer --> committer_services["validator, verifier, coordinator, sidecar, query service"]
  fabric_x_committer --> committer_dbs
  committer_dbs --> yugabyte_master["YugabyteDB master"]
  committer_dbs --> yugabyte_tablet["YugabyteDB tablet"]

The validator and query service both reference yugabyte_cluster_ref_id: 1, which points them at the YugabyteDB hosts under committer_dbs.

PostgreSQL is still present for Fabric CA state, but it is not the committer storage backend. Monitoring omits the PostgreSQL exporter used by PostgreSQL-backed local inventories.