Data Flow
Data Flow Architecture
Playnance games are designed around event-driven, real-time data movement. Every user action, game event, and blockchain transaction flows through a layered pipeline that prioritizes speed, determinism, and observability.
This section explains how data moves across PlayBlock — from external game providers and on-chain smart contracts, through internal services, and out to real-time user interfaces and analytics systems.
1. External Inputs & Game Providers
Playnance integrates with external APIs for certain game verticals and partners.
These APIs provide:
Game actions (bets, wins, round results)
Player session events
Provider-specific metadata and callbacks
All external data enters through validated API gateways, where:
Requests are authenticated
Payloads are normalized
Idempotency and replay protection are enforced
This ensures external variability never leaks into core settlement logic.
2. Core Application Services
Once validated, data is processed by internal services responsible for:
Game logic
Bet execution
Settlement orchestration
Risk and limits enforcement
These services are fully decoupled and communicate asynchronously, allowing the system to scale horizontally without tight coupling.
3. Messaging & Event Distribution (Kafka)
At the heart of PlayBlock’s internal data flow is Apache Kafka.
Kafka is used to:
Distribute game events between services
Decouple producers (games, executors) from consumers (analytics, payouts)
Guarantee ordered, replayable event streams
Absorb traffic spikes without back-pressure
Every meaningful system action becomes an event:
Bets placed
Wins settled
Games finalized
Treasury movements
This event-first design is critical for reliability and auditability.
4. Fast Access & State Caching (Redis)
For low-latency operations, Playnance relies heavily on Redis.
Redis is used for:
Hot state caching (sessions, balances, game state)
Deduplication and idempotency keys
Rate-limiting and locks
Short-lived coordination data between services
Redis allows services to operate at sub-millisecond latency without constant database or blockchain calls.
5. Operational Storage & Logs (MySQL)
Structured operational data is stored in MySQL.
MySQL is the source of truth for:
Players and accounts
Game metadata
Financial logs
Provider requests and responses
Audit and reconciliation records
This layer prioritizes consistency and traceability over raw speed.
6. On-Chain Event Indexing (ClickHouse)
Smart contracts deployed on PlayBlock emit a high volume of on-chain events.
These events are:
Collected via JSON-RPC and WebSocket listeners
Normalized by sync services
Written into ClickHouse
ClickHouse is optimized for:
Massive insert throughput
Time-series queries
Historical analysis
Cross-contract analytics
This separation keeps analytics workloads from impacting live gameplay.
7. Real-Time Streaming to Clients (PieHost)
To power live experiences, PlayBlock streams selected events in real time via PieHost.
Used for:
Live odds and price updates
Order books and liquidity changes
Game state transitions
User-facing dashboards
This enables WebSocket-based, sub-second updates without polling or API overload.
8. Blockchain Transparency (Blockscout)
All on-chain activity on PlayBlock is publicly observable via Blockscout.
Blockscout provides:
Transaction visibility
Smart contract inspection
Event logs
Treasury and executor transparency
This ensures PlayBlock remains verifiable, auditable, and trust-minimized.
End-to-End Flow Summary
External API or user action enters the system
Core services validate and process the request
Events are emitted to Kafka
Redis supports fast state access
MySQL stores operational truth
Smart contracts emit on-chain events
ClickHouse indexes events for analytics
PieHost streams live updates to clients
Blockscout exposes everything publicly
This data flow design allows PlayBlock to achieve:
High throughput without bottlenecks
Deterministic settlement
Real-time user feedback
Strong auditability
Clean separation between gameplay, analytics, and infrastructure
It is purpose-built for gaming, finance, and real-time blockchain systems.
Last updated
Was this helpful?

