processor

Processor Service

The processor service consumes test events from NATS JetStream and persists relational run data to PostgreSQL. MongoDB is retained only for the live step buffer used while tests are still in flight.

Architecture

The processor service handles:

1. Consuming test events from NATS JetStream
2. Writing structured run, suite, test, attempt, and attachment data to PostgreSQL
3. Maintaining a MongoDB-backed live step buffer until test completion
4. (Future) Uploading artifacts to object store
5. (Future) Emitting summaries for fast UI queries

Current State

Currently, the processor service runs as a NATS consumer with PostgreSQL persistence and MongoDB-backed live buffering. It requires NATS, PostgreSQL, and MongoDB.

Running

With PostgreSQL + MongoDB + NATS (required)

Start infrastructure:

docker compose up -d postgres mongodb nats

Then run the processor:

make build-processor
DATABASE_URL='postgres://observer:observer@localhost:5432/observer?sslmode=disable' \
MONGODB_URI='mongodb://root:password@localhost:27017/observer?authSource=admin' \
NATS_URL='nats://localhost:4222' \
./bin/processor

Environment Variables

Database

The processor writes relational data through the PostgreSQL repository. MongoDB is used only for the live step buffer collection.

Future Enhancements

• Object storage integration (MinIO/S3)
• Summary generation and caching
• Consumer group scaling
• Metrics and tracing