Software Architect · iGaming · High-Load Systems
I design and build backend systems that handle money, traffic and failure without blinking.

Backend engineer and architect with 8+ years in software, specialising in iGaming and high-load distributed systems. I started in mobile (Android, Kotlin Multiplatform) and moved down the stack to where the hard problems are: transactional consistency, throughput, latency and reliability of systems that process real money in real time.

I think in domains first and frameworks second. Clean boundaries, explicit contracts and event-driven communication are how I keep large systems understandable as they grow.

• iGaming platforms — casino and betting backends: player accounts, wallets, payments, game provider integrations, bonuses and engagement, back-office tooling
• High-load backends — services built for high RPS, low latency and horizontal scale
• Financial-grade transactions — idempotency, exactly-once effects, ledgers, reconciliation
• Distributed architecture — microservices, event-driven design, gRPC contracts, multi-tenant systems
• Cloud infrastructure — Kubernetes, GitOps, infrastructure as code, observability

• Domain-Driven Design, Clean / Hexagonal Architecture, CQRS
• Event-driven integration over shared databases
• Contract-first APIs with gRPC and Protobuf
• Architecture rules enforced by tests, not by convention
• Observability from day one: metrics, tracing, structured logs

Languages: Java, Kotlin, Rust, TypeScript
Frameworks: Spring Boot, Ktor, tonic, Vue
Messaging & APIs: gRPC, Protobuf, RabbitMQ, Kafka, WebSockets
Data: PostgreSQL, Redis
Infrastructure: Kubernetes, ArgoCD, Terraform, AWS, Docker, Grafana, Prometheus

Open to architecture consulting and challenging high-load projects. Reach me on X.