Tamper-evident audit log

Lock 17
HTTP/2Users5,000 req/sAPI server2 vCPU · 1 GBWorker1 vCPU · 1 GB × 4
HTTP/2HTTP/2Users5,000 req/sAPI server2 vCPU · 1 GBWorker

Turn every goal green.

Traffic
5,000 req/s · writes only
Limit
API server answers about 6,700 req/s
Bill
  • API server8 USD/mo
  • Worker16 USD/mo
24 of 60 USD/mo

Goals

Not tested yet

Events that arrived in the wrong order.The share of requests that fail or get no answer.Saved data that was lost later.How long a message waits before a worker takes it.99 of 100 requests finish faster than this.What the servers and services cost each month.

Services send 5,000 audit events/s, 6 KB each, from 2,000 actors. Each actor's events form a hash chain, appended in order. The chain writer runs in a locked vault in us-east. A log partition carries 10 MB/s. Keep order, lose nothing, p99 under 50 ms, lag under 2 s.

A graph for each resourceTap to add or remove the probes

One CPU graph · CPU 40% · disk no graph · the fault is hidden

Parts you can add: Kafka log, Managed queue, Worker, Message broker. At most 6 parts. Budget: 60 USD/mo.

Tap a part to add it, or drag it onto a trace.Click a part to add it, or drag it onto a trace.