Skip to content
ArtificialFlow

Architecture

A browser modeler, a command API, a runtime, a query API, and a sync worker. Node.js, .NET, and Java speak the full API. Python and Go run workers. Identity is your OIDC provider, or no IAM at all.

Components

ComponentResponsibility
FrontendBPMN modeler, dashboards, a read-only identity view, and workflow operations.
GatewayOne HTTP entry. / goes to the frontend, /api/ to command, and /api/query/ to query.
CommandWorkflow writes, worker and user-task APIs, identity endpoints, the outbox, and local console login when IAM is off. It applies database migrations at startup.
RuntimeTimers, jobs, and pending execution. It relays the transactional outbox to Kafka in batches.
Sync workerProjects Kafka events and Debezium records into Elasticsearch with bulk writes.
QueryRead-optimized process and instance data from Elasticsearch. Those views are eventually consistent.
IAMOptional. IAM_DEPLOYMENT_MODE=true validates tokens from your OIDC provider. false has no provider.

Postgres is the source of truth. Command and runtime apply migrations at startup under one Postgres advisory lock. There is no separate migration job.

Request flow

  1. People open the frontend through the gateway.
  2. With true, the browser authenticates at your OIDC provider. With false, the console uses the local sign-in and the API needs no token.
  3. Command APIs handle writes and emit outbox records.
  4. The runtime and external workers execute jobs.
  5. The sync worker projects changes into Elasticsearch.
  6. The query API serves dashboards and instance views.

One Compose file, one chart

docker-compose.yml is the local stack: Postgres, Elasticsearch, Kafka, Debezium, and the ArtificialFlow services. charts/artificialflow is the Kubernetes chart. It bundles those same dependencies by default. Turn each one off when you already run it. Elasticsearch is the only search backend. Kafka with Debezium is the only event transport.

Clients: Node.js, .NET, and Java cover the API, workers, and user tasks. Python and Go are workers only.

Production should put Postgres, Kafka, Elasticsearch, secrets, TLS, backups, and observability outside the evaluation defaults. The accepted design notes in the repository cover migrations, runtime ownership, tenants, instance migration, and the HTTP contract.