Diagram Distributed Apache Ignite Cache Schemas

Ignite projects its partitioned in-memory caches as SQL schemas and tables. DbSchema connects with the thin JDBC driver, reads those cache-table mappings across the cluster, and renders them as an interactive ER diagram.

Cache-to-table mappings as a diagram, not configuration XML
Run collocated joins and distributed aggregations from a desktop GUI
Inspect cache entries without Visor or the control center
Reach multi-node clusters through failover addresses in one URL

available for

ISO-27001 certified

Free Community Edition No signup required 15-day Architect trial included

Free Download

DbSchema drawing Apache Ignite cache tables as an ER diagram

Trusted by teams at

Gigabytes in Memory, Spread Over Nodes
And No Picture of What's in There

An Ignite cluster holds its working data in partitioned caches across machines. Auditing that data model usually means querying system views or picking apart the cluster configuration XML — neither of which anyone volunteers to do.

DbSchema asks the SQL catalog instead, and turns the cache-backed tables into a diagram the whole team can read.

Query, Inspect & Document
a Cluster That Lives in RAM

Desktop tooling for data that never touches a disk.

Build queries on Apache Ignite cache tables in DbSchema

Point and Click at Cache Tables

Build queries over cache-backed tables graphically — filters, grouping, joins — and read the SQL DbSchema generates before it hits the cluster.

Run distributed SQL on Apache Ignite from the DbSchema editor

Distributed SQL From Your Desktop

Write collocated joins, distributed aggregations, and cross-cache queries in the editor — no separate Ignite client application, no shell session.

Document the Apache Ignite SQL schema with DbSchema

Publish the Cache Catalog

Generate documentation of the Ignite SQL schema — tables, columns, key mappings — for backend teams who consume the caches but never configured them.

Volatile Memory,
Durable Schema History

Cache contents come and go with the cluster; the model file does not. Keep it in Git and the mapping of caches to tables gains what memory lacks — a history your team can diff, review, and reason about release after release.

Apache Ignite schema model tracked in Git with DbSchema

Read Git Workflow Docs

Thin-Client Connection on Port 10800

DbSchema uses the Ignite JDBC thin driver, which connects like any external tool — it starts no embedded Ignite node inside the client process. The URL is jdbc:ignite:thin://host:10800/schema, with 10800 as the default thin-client port; for a multi-node cluster, list the addresses for failover: jdbc:ignite:thin://host1,host2:10800/schema. On connect, DbSchema lists the cache-backed tables straight away.