Datomic Cloud Architecture

Datomic's data model - based on immutable facts stored over time - enables a physical design that is fundamentally different from traditional RDBMSs. Instead of processing all requests in a single server component, Datomic distributes transactions, queries, indexing, and caching to provide High Availability, horizontal scaling, and elasticity. Datomic also allows for dynamic assignment of compute resources to tasks without any kind of preassignment or sharding.


A complete Datomic installation is called a System. A System consists of:


Storage Resources

The durable elements managed by Datomic are called Storage Resources, including:

  • the DynamoDB Transaction Log
  • S3 storage of Indexes
  • an EFS cache layer
  • operational logs
  • A VPC and subnets in which computational resources will run

These resources are retained even when no computational resources are active, so you can shut down all the active elements of Datomic while maintaining your data.


Primary Compute Resources

Every running system has a single set of Primary Compute Resources which provide computational resources and a means to access those resources. Primary Compute Resources consist of:

  • Primary Compute Nodes dedicated to transactions, indexing, and caching.
  • Route53 and/or Application Load Balancer (ALB) endpoints
  • a Bastion Server

The specific composition of Primary Compute Resources is determined by your choice of Topology: either Solo or Production. The Datomic programming model is entirely the same in both Solo and Production Topologies.

Solo Topology


The Solo Topology provides an inexpensive way to access Datomic's full programming model for development, testing, and personal projects. The Solo Topology includes Storage Resources plus the following Primary Compute Resources:

  • a dedicated VPC
  • a Route53 endpoint
  • a single t2.small Node
  • a Bastion Server

Production Topology


The Production Toplogy includes Storage Resources plus the following Primary Compute Resources:

  • a Route53 endpoint
  • an Application Load Balancer for High Availability (HA)
  • two or more i3.large Nodes
  • a Bastion Server

The Production Topology also allows for the addition of optional Query Groups for different loads (e.g. transactional vs. analytic vs. developer queries). Query Groups can AutoScale to meet changes in demand.


Nodes are the computational resources for a Datomic System. Nodes provide


For security, Datomic nodes all run inside a dedicated VPC that is not accessible from the internet. To provide e.g. developer access to a system, you can configure a bastion server that is open to a range of IP addresses outside the Datomic VPC, forwarding traffic to Datomic nodes.