Senior Software Engineer specializing in distributed, high-concurrency, and event-driven systems— from real-time iGaming platforms to FinTech and Web3 payment infrastructure built with Node.js, TypeScript, NestJS, Go, .NET, PostgreSQL, and MongoDB, with production cloud experience across Azure and Google Cloud Platform.
01 · System design
An illustrative reference system based on the service boundaries, data flows, and failure modes I work with. Hover or focus a node to inspect its responsibility.
Server-authoritative game logic, secure outcomes, and low-latency bet settlement.
Real-time · RNG02 · Execution history
Each role added a new layer: data-intensive services, distributed boundaries, then platform-level ownership across gaming and payments.
Splash Software · Dubai
Architecting white-label iGaming, real-time game engines, high-volume data paths, and Web3 payment infrastructure across regulated markets, with production delivery on Azure and GCP.
ITFAQ · Dubai
Led monolith decomposition, built performance-critical services, and delivered industrial hardware integrations and complex data migrations.
Tatweer LLC · Damascus
Developed distributed services, ERP workflows, and live CRM synchronization for large user and data environments.
03 · How I think
A live walkthrough of how I would frame, design, scale, and operate a system serving 50,000 concurrent players.
What does 50,000 concurrent players actually mean?
Concurrent connections are not the same as commands per second. I separate connection fan-out, bet-command throughput, game-loop latency, financial correctness, and regional availability before selecting technology.
Unproven peak assumptions
Confusing connected users with write throughput
Measure the workload before drawing the boxes.
04 · Selected systems
The architecture, engineering constraint, and ownership behind platforms built for throughput, correctness, and operational clarity.
Open-source runtime architecture visualizer for Node.js and NestJS. NodeFlow discovers real execution paths, services, databases, messaging, and external dependencies at runtime, backed by a Go collector and topology engine.
A multi-operator tournament engine with live leaderboards, dynamic rewards, and reliable asynchronous orchestration.
A payment orchestration layer for fiat and crypto deposits, withdrawals, reconciliation, and treasury operations.
One backend ecosystem serving multiple operators, brands, markets, games, and regional policy sets.
05 · Technology topology
I choose technology around data shape, consistency needs, failure modes, team boundaries, and the cost of operating it at scale.
Runtime choices shaped by latency, team ownership, and operational constraints.
Service contracts across request/response and real-time communication paths.
Event pipelines designed for idempotency, retries, ordering, and backpressure.
Storage models selected around consistency, access patterns, and growth.
Containerized delivery, autoscaling, and observable cloud operations.
Patterns for systems that stay understandable while traffic and teams grow.
06 · Engineering notes
Practical notes on distributed systems, data architecture, and backend engineering.
06 · Open channel
I’m interested in senior software engineering and architecture roles where reliability, financial correctness, real-time behavior, and scale genuinely matter.