Our Architecture
Our modular architecture embeds a secure, immutable blockchain data layer directly inside the application.
Three Core Pillars of the Architecture
The architecture is anchored by three tightly integrated core components, governed by a highly standardized operational model, that delivers a single source of truth, eliminates logic duplication, and enables rapid, low-effort adaptation of new business domains.
1. Highly Standardized Blockchain Engine The single leader (Execution Engine) is purpose-built for atomic, controlled writes: it sequences events deterministically (via Proof-of-History in 400 ms slots), appends them immutably to the append-only ledger (binlogs), and guarantees full auditability. No multi-party consensus overhead — only one trusted writer for predictability and simplicity.
2. Business Logic Library All domain-specific rules and calculations live here — written in pure Rust (recommended for reliability and performance), but can be JavaScript, or any other language you prefer. No duplication across layers: product flow orchestration, validations, checks — everything is coded once and reused natively. Programs remain small and auditable.
3. In-Memory Replica The read-optimized powerhouse: an always-current, RAM-based view of application state rebuilt exclusively from ledger events. All queries (balances, histories, statuses, BI views) hit this ultra-fast copy — delivering sub-3 ms user-facing reads with zero disk I/O. This asymmetry is key: writes stay secure and controlled, while reads scale independently without impacting performance — even under heavy reporting loads. Sync modes adapt flexibly to volume, and in our single binary but internet-based PoC Spark Go everything runs so fast, blink once and you have missed the update.
Flexible Compositions for Enterprise Needs
While the foundation is a tightly controlled, single-leader model (400 ms slots, deterministic sequencing), the architecture allows a broad spectrum of compositions tailored to your scale, domains, and performance goals.
- Standalone Applications
Each business application (loyalty, CRM, supply chain module, etc.) runs with its own Execution Engine and local in-app Replica. This delivers zero-latency reads and simplest possible deployment — ideal for independent workflows or smaller-scale use. - Company-Wide Replica Sharing
Multiple standalone apps each maintain their own engine and application Replica, but on top feed events into a shared, enterprise-level Replica. This creates a real-time, aggregated company state — perfect for cross-application business intelligence, dashboards, and analytics — without ever compromising individual app speed or isolation. - Shared Engine + Central Mempool
Several business logic libraries (e.g. Administrative functions, HR processes, procurement logic) submit events to one central Execution Engine and mempool. The single leader sequences and executes everything — preserving full control while enabling seamless, unified operations across multiple domains in medium to large enterprises. - Scaling Directions
- Vertical scaling: Increase CPU cores and RAM on the leader and replica nodes. Standard server hardware already supports hundreds of transactions per second comfortably — high performance remains affordable without specialized infrastructure.
- Horizontal scaling: Add multiple read replicas (synchronized via gossip or broadcast) for read-heavy workloads, or evolve to multi-leader setups in advanced scenarios — always under strict, centralized governance.
- Geographic sharding: Only required in rare cases with millions of highly concurrent users; regions can be sharded while preserving the controlled leader principle.
- Controlled Multi-Party Extensions (when needed)
Participants submit events to the central leader's mempool instead of performing their own writes — creating a far more robust and auditable system than conventional distributed networks. Shared program responsibility is possible, but requires careful governance to prevent complexity traps such as the "tragedy of the anticommons".
“Blockchain is no longer something you connect to... It is now something you write!!”