I am a software engineer focused on backend engineering, cloud-native architecture and platform-oriented systems.
My work usually sits at the intersection of:
- distributed systems
- event-driven architecture
- financial-grade backend services
- infrastructure as code
- observability
- clean architecture
- developer experience
I like systems that are not only functional, but also traceable, scalable, testable and boring enough to run in production.
Business complexity
β
βΌ
Clean domain modeling
β
βΌ
Observable backend services
β
βΌ
Event-driven integration
β
βΌ
Cloud-native deployment
β
βΌ
Production feedback loop| Backend | Java, Spring Boot, Quarkus, Kotlin, Node.js, TypeScript |
| Architecture | Microservices, Hexagonal Architecture, DDD, Event-Driven Systems |
| Cloud & Infra | AWS, Docker, Kubernetes, Terraform, LocalStack |
| Data | PostgreSQL, OracleDB, MongoDB, Redis, DynamoDB |
| Messaging | SQS, SNS, RabbitMQ |
| Observability | Datadog, ElasticSearch, structured logs, metrics and production diagnostics |
| Project | Main idea | Stack / Theme |
|---|---|---|
order-flow-platform |
Platform architecture and cloud solutions study case | Java, architecture, cloud |
qtwitch |
Twitch API simulator with streaming concepts | Java, Quarkus, REST API, SQL |
exodia |
Security-oriented CLI experimentation | JavaScript, CLI, security |
portfolio |
Personal portfolio | TypeScript, React, Next.js |
mt-rabbit |
Message queue sample with RabbitMQ and MassTransit | C#, RabbitMQ, messaging |
8-puzzle |
Heuristic search applied to the 8-puzzle problem | Python, BFS, DFS, AI |
Forest |
Data structure studies with trees | Java, binary tree, B-tree, trie |
p2p-chat |
Peer-to-peer chat using sockets | C#, sockets, networking |
engineering:
mindset:
- make_complexity_visible
- design_for_failure
- measure_before_optimizing
- logs_are_part_of_the_product
- tests_are_architecture_documentation
- production_feedback_beats_assumptions
architecture:
- clean_boundaries
- explicit_domain_rules
- event_driven_when_it_reduces_coupling
- infrastructure_as_code
- observable_by_defaultI am sharpening my work around:
- Java and Kotlin backend systems
- AWS production architecture
- Kubernetes-based deployment
- Terraform and reproducible infrastructure
- event-driven platforms
- observability-first engineering
- platform engineering
- architecture portfolio projects
Good software is not just code that works.
It is code that explains itself under pressure.
I value codebases where the architecture is understandable, the operational behavior is visible, and the development flow does not fight the team.

