What do you need?
- Issue in your project?
- I'll handle it.
- System to build?
- I build it.
- Scale problem?
- I solve it.
- Bug hiding in the logs?
- I find it.
No limits. Name it — I'll do it.
Three problems I solve well.
Pick the one that matches yours — each links to a deep dive from real production work.
10,000+ concurrent users on Kubernetes. Custom-metrics autoscaling, pre-warming, JVM cold-start tuning, Redis Pub/Sub fanout.
The first 15 minutes of an incident decide the next 3 hours. A field playbook from years of iGaming on-call.
Owned and led the rebuild of a 20+ microservice polyglot platform into cloud-native. The gotchas plan documents never mention.
I keep high-traffic systems running smoothly.
Platform · observability · alerting · feature work — end to end.
For the last six years I've held the technical ownership of a multiplayer board-game platform serving 10,000+ concurrent users. In 2023 I owned and technically led its rebuild into a Kubernetes + AWS cloud-native architecture — 20+ microservices across Java, .NET, PHP, Python, Node.js and React.
- RoleTechnical owner · iGaming platform
- LocationIstanbul, Türkiye (UTC+3)
- StatusOpen to conversations
How I got here
- 2012–2019First seven years
Multiple companies, multiple teams, multiple stacks. The period that built the end-to-end engineering foundation everything else stood on.
- 2020Technical ownership of a 10k+ CCU platform
Took over the technical ownership of a multiplayer board-game platform serving 10,000+ concurrent users.
- 2023Cloud-native transformation
Owned and technically led the rebuild from on-prem into Kubernetes + AWS across 20+ microservices.
- NowRunning the platform, open to conversations
Delivering features, keeping the system stable, and looking for the next interesting challenge.
A bit about me
I've been writing software professionally since 2012. My strongest muscle is owning a large, noisy, business-critical system end to end — architecture, production stability, incident triage, and long-term technical sustainability.
The 2023 AWS migration wasn't a lift-and-shift. It was a full rebuild of a polyglot distributed platform — 20+ microservices across Java, .NET Core, PHP, Python, Node.js and React — reshaped into a cloud-native, Kubernetes + Istio architecture. The system is live on AWS today, and I still look after its architecture, stability, and evolution.
I care about readable code, solid standards, and documentation that ages well. Over the past year I've leaned on AI-assisted tools like Cursor and Claude Code to roughly 5× my delivery speed — and I think the line between "coding" and "product thinking" is getting healthier because of it.
What I reach for
Cloud-native, microservice-based systems on AWS + Kubernetes with Istio service mesh and Docker across the stack.
Java (Spring), C# (.NET Core), PHP (Laravel/Lumen), Python. High-performance data layer with MySQL, Redis (Pub/Sub, HashMap), RabbitMQ, Memcached.
End-to-end web and mobile. TypeScript, Angular, Vue, React, Node.js, React Native.
CI/CD pipelines with Jenkins, version control with Git, and production error monitoring with Sentry.
A few things I’ve built
A curated slice. Everything — and the source — is on the projects page.
Opinionated backend for real-time multiplayer games. Player auth, leaderboards, rooms, and a modular service layout ready to drop into Traefik.
Dedicated runtime per project with auth, matchmaking, inventory and reward flows. Designed to take a project from zero to production-grade backend in hours.
LiveOps console for game segments, remote config, in-app campaigns, and player inbox. Proxies runtime decisions to live game servers.
End-to-end platform with vehicle inventory, customer tracking, sales analytics, and an AI-assisted sales agent. Built for fleet-scale tenants.
Long-form notes on distributed systems, production stability, AI-assisted shipping. No spam, easy to unsubscribe.
Got a system you want to talk about?
Whether it's a distributed-systems question, a production fire, or an interesting role — I'm easy to reach.