Layered, event-driven and cloud-native
Designed for volume from the first line.
Five layers, each with one job
Decisions that keep it fast and safe
Event-driven, message-based
Native AS4 to the STN and the ATO.
Rules are data
A fee change is a sealed release, not a software project.
One description of every field
Read by screens, checks and the field guide.
No shared databases
Products talk over HTTPS, never through each other's tables.
One design, any stack
The fund chooses the technology without changing the design.
From an analyst's rule to the member's account
A fee is written once, tested and sealed. The Engine loads the release a single time and scores every member in memory, then writes the rows in batches. Each posting names the rule that scored it.
- Analystwrites the fee in Control
- Releaseis tested and sealed
- Engineloads it once
- Evaluatescores each member in memory
- Batchwrites rows with savepoints
- Bookof record, with the rule named
Built for volume
Rules compiled once
A release is loaded into memory once. Every member is scored in the same process: no network call, no re-reading, no re-parsing.
Batched writes
Rows are written in batches with savepoints, so one bad member never throws away the file.
Many workers, one runner
Workers scale across cores and machines against one queue. A new process is a step list, not a new program.
The database does the heavy lifting
Lists, search, sorting and counts run in the database, a page at a time, not in the browser.
Measured on every run
The job clock splits calculation, SQL and I/O, so the next improvement goes where the time is.
Isolation by design
A busy allocation cannot lock out an analyst, and a bad authoring session cannot touch the member book.
Talk to our architects
Walk through the design with the people who built it: the Engine, the release model and how Córas runs at volume.