The APIs I design
- Business APIs carrying the rules of your operation
- APIs consumed by a web front end, a mobile app, or both
- Integration between two systems that did not talk to each other
- Asynchronous exchanges over message queues, when volume demands it
- Documented APIs opened to external partners
- Scheduled jobs and webhooks
What makes an API last
The difference between an API that holds up and one people end up working around is invisible at delivery. It shows at the first change of requirements.
- A documented contract, honoured, and versioned when it has to change
- Explicit errors that say what to fix, not merely that something failed
- Pagination and filtering planned from the start, not bolted on under pressure
- Replayable operations with no side effects, which saves recovery after incidents
- Traces and metrics, so diagnosis does not rely on guesswork
- Tests on business rules, where a regression costs the most
Integration with existing systems
Few projects start from a blank page. I have delivered REST connectors into systems already in place, asynchronous exchanges between applications, and synchronisation between front-office tools and back-office systems, notably on fleet and contract management applications.
Backend projects delivered
A delivery platform with real-time tracking, a two-sided marketplace, and a full migration of a legacy data estate onto a new schema with no service interruption at cut-over.
See the eleven documented projects
Frequently asked questions
REST or GraphQL?
REST in most cases: simpler to cache, to document and to hand over. GraphQL when several very different clients consume the same data and over-fetching becomes a real cost.
Node.js or Spring Boot?
Node.js when the front end is already JavaScript and the team is unified on one language. Spring Boot when the ecosystem is Java, the business rules are heavy, or the environment is tightly governed. I have delivered both.
Do you deliver documentation?
Yes, it is part of the work, not an option. An API without a readable contract forces the next developer to read the source code.