APIs and services
REST APIs with clear contracts: predictable routes, errors that actually say something, consistent responses across projects. And the other side too, consuming third-party services without their failure taking mine down.
Portfolio · Madrid, Spain
Backend developer · Java · Kotlin · Spring Boot
I have been programming for close to three years and I focus on the backend. What interests me is the part underneath an application: how it is structured, how it stores data, and how it behaves when something breaks.
What I work on
REST APIs with clear contracts: predictable routes, errors that actually say something, consistent responses across projects. And the other side too, consuming third-party services without their failure taking mine down.
Data model first, endpoints second. Well-shaped entities, explicit relations, transactions that never leave things half done, and layers you can change one at a time.
As an underlying criterion, not a final coat of paint: validate what comes in, never trust the client, control access and expose no more than needed. I practise it on TryHackMe.
How a request travels
Tooling
Java
Kotlin
Python
SQL
JavaScript
Spring Boot
Hibernate / JPA
REST
WebSockets
Node.js
MySQL
PostgreSQL
MongoDB
JDBC
Git
Maven
Docker
Postman
IntelliJ IDEA
Linux