Go Backend
Production services with explicit boundaries, table-driven tests, and performance-aware code paths.
Open to backend & platform roles
Backend systems that survive production.
I design and build distributed services in Go — event-driven, observable, and resilient to failure.
Creator of TaskForge, a Kafka-backed task orchestration stack.
- End-to-end ownership of services, APIs, and operational runbooks
- Kafka, Kubernetes, PostgreSQL — wired for scale and failure modes
Focus
How I work
Clear interfaces, strong tests, and instrumentation before the incident — not after.
Event-driven
Async flows over Kafka with retries, idempotency, and consumer isolation you can reason about.
Reliability
Metrics, traces, and structured logs — Prometheus, Grafana, Jaeger, OpenTelemetry.
Stack
Technical skills
Languages, platforms, and practices I use in production.
Languages
Go, JavaScript, Python
Backend
REST, WebSockets, GORM
Architecture
Microservices, event-driven, distributed systems
Infrastructure
Docker, Kubernetes (k3s), Nginx, GitHub Actions, CI/CD
Data & messaging
PostgreSQL, Kafka
Observability
Prometheus, Grafana, Jaeger, OpenTelemetry
Experience
Where I build
Current role and education — details on the about page.
Backend Developer (Go)
Privia Security A.Ş
B.Sc. — Computer Engineering
Sakarya University of Applied Sciences
Work
Featured projects
Systems I’ve designed, shipped, and operated.
TaskForge
Distributed task orchestration in Go. Kafka between services, scheduler and retries, WebSockets, PostgreSQL, full observability with Prometheus, Grafana, Jaeger, and OpenTelemetry. Docker/Kubernetes ready.
Repository →
Real-time messaging
WebSocket microservices, Redis Pub/Sub, and Kafka for horizontal scaling and event-driven state on Kubernetes.
Discuss →Writing
From the blog
Production notes on failure-first distributed systems design.
Designing Distributed Systems That Don't Collapse Under Reality
Partial failure, idempotency, retries, DLQs, and observability patterns that hold in production.
Read article →Contact
Let’s talk
Recruiting, collaborations, or technical deep-dives — reach out via email or social.