API integrations & backend development
I build, secure and integrate REST APIs and backend services, mainly with Java 17, Spring Boot and Kotlin, and I have maintained Laravel APIs on a live e-commerce platform.
What I build
- REST APIs and microservices in Java 17, Kotlin and Spring Boot, or in Laravel and Django REST Framework when a project already uses them.
- OpenAPI specifications that frontend teams and partners can build against.
- Authentication and access control with Keycloak, Spring Security, JWT and OAuth2.
- Messaging between services with RabbitMQ or Kafka, with circuit breakers for failing dependencies.
- Integrations with third-party services through their APIs and webhooks, including messaging and email providers.
In professional work
Vast-Security — Full-Stack Software Engineer
- Built and maintained microservices with Java 17, Kotlin, Spring Boot, Spring Cloud Gateway and Config, and MongoDB.
- Wrote the OpenAPI specification for a risk assessment API with more than 60 endpoints, and integrated it into Angular dashboards.
- Secured API endpoints and communication between services with Keycloak, using custom roles and claims.
- Implemented messaging between services with RabbitMQ, with circuit breakers to handle service failures.
La Maison Marocaine du Livre
- Maintained backend APIs for a live e-commerce platform with Laravel, MySQL and Redis.
- Reduced catalogue query and page load times by caching data in Redis and reworking slow database queries.
- Deployed services with Docker and Docker Compose on a Linux VPS behind reverse proxies.
Java 17 / Kotlin / Spring Boot / Spring Cloud Gateway / OpenAPI / Keycloak / RabbitMQ / MongoDB / Laravel / MySQL / Redis / Docker
In project work
Project experience, separate from the professional roles above.
- WanderWise: Spring Boot microservices with Eureka and Kafka, JWT and OAuth2, Flyway migrations, OpenAPI documentation and Docker deployments with GitHub Actions.
- Onyx: Spring Boot backend with Spring Data JPA, Spring Security and JWT, plus real-time data over WebSocket STOMP.
- iMohami: Django REST Framework API with JWT authentication and PostgreSQL, including billing logic for dashboards and client portals.
- WhatsApp Audio Replies & Automated Follow-Ups: WhatsApp messaging through Evolution API, driven by incoming webhooks and scheduled reminders.
- Website Lead Capture & Telegram Alerts: Webhook contract between this website’s server and n8n: validated payloads, a stable submission ID and explicit delivery responses.
Kafka / Eureka / PostgreSQL / Django / GitHub Actions
Web applications and dashboards
An API usually serves screens that people use every day. Dashboards, client portals and internal tools have their own page:
- Web application development: Angular and React interfaces, from monitoring dashboards to client portals.
n8n workflow automation
When the job is connecting existing tools rather than building a new API, an n8n workflow is often quicker to set up and change:
- n8n workflow automation: lead capture, approval flows, WhatsApp messaging and support email drafts.
Questions
Does my project need an API, a web application or n8n?
A web application provides the screens people use. An API handles data and business rules. n8n connects repeatable steps across existing tools. A project can combine them; the choice depends on the interfaces your tools expose and the decisions that need human review.
Can you work on an existing codebase?
Yes. I maintained Laravel APIs on a live e-commerce platform and fix production bugs in Spring Boot services. The first step is reading the code and its documentation to agree what can change safely.
What should I share when requesting an integration?
Describe the current process, the systems involved, a sample of the data with private values removed, API documentation if available, and what should happen when a step fails. Share credentials through an agreed secure channel, rather than the contact form.