AnantState
For the CIO, CTO and platform leaders

It fits the estate you already run.

AnantState runs in your own cloud account or network, on a standard relational database, and reads events from the systems you have. Your warehouse stays yours, and a new domain is a definition your team can read and change.

In plain termsYour cloud, your network, your warehouse.

At a glance

  1. Three topologies

    Single-host containers, Kubernetes, or your cloud account with a managed database.

  2. Events from where they live

    Streams, REST sources, scheduled pulls or bulk import.

  3. A definition, not a fork

    A new area of the business is configuration your team can read and change.

  4. Observable

    Health, throughput and latency exposed as metrics for your operations team.

The questions architecture asks

  • Where does it run, and what does it need from us to run?
  • How do events get in, and what happens to the ones that fail?
  • What does it replace, and what does it sit beside?
  • How do we customize it without forking it?

Three supported topologies, the same services

Three supported topologies, the same services

  1. DatabaseIn: Single-host containers
  2. API serviceIn: Single-host containers
  3. Web applicationIn: Single-host containers
  4. Identity provider: Optional, for testingIn: Single-host containers
  5. The same services: Deployed to a cluster you already runIn: Kubernetes
  6. Application servicesIn: Cloud with a managed database
  7. Managed database: An instance your team already operatesIn: Cloud with a managed database
  8. Provisioning and retention scriptsIn: Cloud with a managed database
  9. Keycylinder: A standard relational database; stack: The same services; external: Optional
The same services run in each topology. What changes is how they are hosted, and in every one the store is a standard relational database.

However an event arrives, it lands the same way

Every route lands as an event

  1. Streaming: A live stream; state advances in real timeLeads to: An event
  2. REST source: A system can push, or be polled, over HTTPLeads to: An event
  3. Scheduled pull: A warehouse or batch system holds the historyLeads to: An event
  4. File or bulk import: Backfilling a population for a new domainLeads to: An event
  5. An event: Attributed to a domain, mapped to an entityLeads to: State update; Dead-letter view (could not be mapped)
  6. State update
  7. Dead-letter view: What could not be mapped, with the reason
  8. Keyqueue: Where every route converges; cylinder: Stored state; external: Kept in view, not lost
However an event arrives, it ends up in the same place: attributed to a domain, mapped to an entity and turned into a state update. What cannot be mapped is kept in view, not lost.

Concerns architecture is likely to raise

The concernThe answer
Another platform to run.In every topology the store is a standard relational database, and a vanilla install is a fully supported target. Migrations run at boot.
Lock-in.Your warehouse stays yours, and a domain is a definition in your own vocabulary rather than code in ours.
An integration project.A connector is a convenience and nothing depends on one. If a system can emit an event or answer an HTTP call, it can be a source.
Upgrades.An upgrade does not require your data to be migrated first.

Bring your topology

Bring:

  • Your target topology
  • Two or three event sources

You leave with how events would land, and where it would run. We don’t publish a deployment timeline, so we will say what a first domain would need.

Bring your topology and your event sources

We will map how events would land and where it would run.