Frankwel Y.

In a team of 18 people divided into two sub-teams (migration and business) and in an Agile context (4-week sprints), we were responsible for the gradual decommissioning of an existing cost optimization application with a Monolithic architecture in favor of a better-sized, more scalable, and more functional application with a Microservices architecture.

- Discussions with business stakeholders for the breakdown of the IS into Microservices by functional domains (DDD).

- Creation of 18 microservices in Java 17 and Spring Boot 3 following clean code principles.

- Use of Spring Security 6 for managing access permissions to REST APIs via tokens.

- API documentation with Open API (Swagger), Use of Spring Boot Actuator for monitoring.

- Use of Kafka for asynchronous communication between Microservices.

- Creation of Dockerfile / Deployment on Kubernetes / Update of existing CI/CD jobs.

- Development of background tasks using multithreading.

- Implementation of an in-memory cache to optimize processing and limit database access.

- Compression of REST API responses.

- Implementation of a Java code formatter to facilitate code reviews.

- Implementation and sharing of best practices to improve code quality (organization of regular meetings to discuss SOLID principles, records, pattern matching, type inference, etc.).

- Development of unit tests with a minimum coverage of 80% (TDD, JUnit5, Mockito).

- Development of integration tests with Cucumber (BDD).

- Use of SonarQube to verify code quality and test coverage.

- Use of Checkmarx to detect potential vulnerabilities and security flaws.

In my role as a Java Developer and Co-Tech Lead in a team of twenty (20) people split between Rennes and Paris, we were responsible for the redesign of the subscription and billing management system for the virtual telecom operator La Poste Mobile into a Microservice architecture with a more adequate sizing for the need.

- Prioritization of tickets between Build and Run activities.

- Participation in the creation of project specifications, including the technical architecture document.

- Maintenance of existing batches (Payment defaults processing, Payment rejection, Recovery plan, etc.).

- Development of twenty-two (22) Microservices in Java 11 and Spring Boot 2 for managing the entire subscription process up to mobile line activation.

- Development of nine (9) Microservices in Java 17 and Spring Boot 3 for managing outgoing and incoming portability processes.

- Implementation of an API Gateway with Spring Cloud Gateway.

- Client deliveries and production support in the evenings or on weekends.

- Use of Redis as a caching system and for communication between Microservices.

- Use of Redis Sentinel to ensure Redis high availability.

- Use of Flyway for database versioning.

- Monthly sharing sessions on functional and technical topics.

Within the luxury giant Christian Dior Couture, I joined a team of 8 people to implement order management APIs, used by the group's various entities (sales, rentals, order issuance, payment management, shipping, delivery tracking, after-sales service management, etc.). All this in an Agile SCRUM context with 3-week sprints.

- Regular exchanges with functional teams to confirm needs.

- API documentation via the Anypoint Design Platform.

- Participation in various API developments documented using Anypoint Studio: database querying, interaction with external systems, data transformation, etc.

- Participation in integration phases.

- Demonstrations at the end of each Sprint.

Technologies and tools:Java 8, MuleSoft 4, MUnit, Anypoint API Manager, Anypoint Platform, Anypoint Studio, API, Git, Microsoft Azure DevOps, Agile SCRUM Methodology.