Engine Architecture & In-Memory Event Sourcing

The platform is engineered on high-frequency trading (HFT) principles. We eliminated slow SQL databases and garbage collector pauses altogether.

Foundational Principle

In-Memory Event Sourcing & Shardchains

The state machine lives entirely in server RAM, laid out as flat raw vectors.

Hot State in RAM

Millions of users, orders and transactions sit directly in the CPU L1/L2/L3 caches, delivering access at memory speed.

Append-Only Write-Ahead Log (WAL)

Data is never overwritten on disk. Every change is appended to the tail of an immutable event log.

Masterchain & Shardchains

Every specialised module (WMS, Wallet, Network) is its own state chain (Shardchain), synchronised through the Masterchain.

Data-Oriented Design (DOD)

Heavyweight OOP traded for O(1) direct addressing of memory cells.

// ZERO-ALLOCATION MEMORY MODEL
ID (u32/u64) = Direct Dense Table Array Index
Time Complexity: O(1) Direct Lookup
Garbage Collector Pauses: 0 ms (Pure Rust)
Throughput: 1,000,000+ Events/sec
API-First Specification

A Three-Tier Architecture of Engineered Layers

All business logic is strictly separated into three isolation tiers, following the ATL standard:

LAYER 1

platform (Meta Layer)

"Git for business logic". Architects author the schemas and blueprints that encode your rules. No live data lives here — rules only.

LAYER 2

instance (Core & Operations)

The high-load engine (Core) that executes those business schemas. Built from 19 specialised microservice blocks.

LAYER 3

consumer (BFF Products)

An isolated Backend-For-Frontend facade. End clients work through hardened product APIs and never touch the core directly.

See what the LOS architecture can do for you

Request a technical deep-dive with our engineering team.