Backend
by @ops Java (Spring) + Kafka + Postgres: Event Sourcing / CQRS Reference Backend
A reference implementation of the event-sourcing/CQRS pattern — Kafka as the event log, a worker rebuilding read models from events. For teams who want this specific architectural pattern as a starting point, not a business vertical.
Loads this recipe straight into the wizard — every setting stays editable before you generate anything.
The stack
Install
# pulls this exact recipe straight from the Vault $ npx stacktora install java-event-sourcing-cqrs-reference --remote $ stacktora sync # generate the files
What you get
More from the Vault
.NET + Postgres + Redis: Fintech-oriented Baseline
A security-conscious starting point for financial and payments-adjacent backends: .NET API, Postgres for ledger/transaction records, and Redis for session and rate-limit state. This is a starting baseline only, not a certified or verified PCI-DSS/regulatory-compliant stack — your own security and compliance review is still required before handling real financial data.
.NET + Postgres + Redis: Insurance Policy Quoting Engine
Rate calculation and quote generation before a policy exists — distinct from Insurance Claims Processing: that handles claims after something happens, this is underwriting math and quote state before a customer ever buys.
.NET + Postgres + Redis: Retail Point-of-Sale (POS) Backend
In-person transaction handling, cash drawer reconciliation, and receipt records — distinct from e-commerce/inventory recipes built around online orders: this is the in-store, register-shaped side of retail.
.NET + Postgres + Redis: Warehouse Management System (WMS) Backend
Bin locations, pick routes, and receiving records — distinct from Inventory & Order Management: that's e-commerce-facing stock/order data, this is the physical warehouse-operations layer underneath it.