Clean architecture
Decoupled systems that isolate business logic from infrastructure and frameworks.
My journey is guided by the belief that code is just a tool to solve complex business problems. With solid experience in the Java and Spring ecosystems, I focus on systems that work AND are easy to maintain and evolve.


My journey is guided by the belief that code is just a tool to solve complex business problems. With solid experience in the Java and Spring ecosystems, I focus on systems that work AND are easy to maintain and evolve.
Specialised in robust APIs and critical integrations, I believe technical maturity shows up in balanced decisions that weigh innovation against real business needs.
I chase real impact: Clean Code is not aesthetics, it is an economic necessity for long-term product sustainability.
Decoupled systems that isolate business logic from infrastructure and frameworks.
System connections focused on resilience, failure handling, and data consistency.
Code that prioritises human communication and easy reviews.
Choices based on facts, business needs and real constraints.
Translating technical complexity into language every stakeholder understands.
Constant learning applied to technical and process improvement.
High-volume financial transaction processing with sub-second latency.
Marketplace centralisation for unified stock and orders.
Controlled migration from a legacy monolith into microservices.
Mastery of the tools that enable scalable, secure solutions.
Writing is how I organise technical thinking and share perspective.
View all articlesHow to guarantee at-least-once delivery without distributed transactions.
Why over-engineering is often the fastest path to project failure.
TestContainers strategies to keep CI/CD fast without losing confidence in your code.