I map complex business domains into resilient, observable JVM services — charting clear routes through distributed systems, data pipelines and high-traffic APIs.
I'm a backend engineer who treats architecture like cartography: before writing a line of code, I want to understand the terrain — the domain boundaries, the data flows, the failure modes hiding in the valleys.
For the past eight years I've built and operated Java and Kotlin services on the JVM, from Spring Boot microservices handling payments and logistics to event-driven platforms streaming millions of messages through Kafka every hour. I care deeply about clean domain models, sensible API contracts and systems that are boring to operate at 3 a.m.
I'm happiest when profiling a hot path down to its allocations, untangling a legacy monolith into well-scoped services, or mentoring teammates on testing and observability practice.
| Discipline | Backend / Distributed Systems |
| Primary Stack | Java 21, Spring Boot 3, Kafka |
| Datastores | PostgreSQL, Redis, Elasticsearch |
| Terrain | Fintech, Logistics, SaaS |
| Base | Warsaw, Poland |
| Status | ● Open to new routes |
A double-entry payment ledger built on event sourcing. Every transfer is an immutable event, projections rebuild balances in seconds, and idempotency keys guarantee exactly-once settlement.
A fleet route-optimisation service for a logistics operator. Reactive WebFlux endpoints, a constraint solver for delivery windows, and a Redis geo-index for live vehicle positions.
Led a strangler-fig migration of a 900k-line legacy Java EE monolith into 14 Spring Boot services on Kubernetes, with zero-downtime cut-overs and contract tests guarding every boundary.
An internal open-source starter that wires OpenTelemetry tracing, structured logging and RED-metric dashboards into any Spring Boot service with a single dependency.