Saybou Doucoure

In a high-stakes project, I am a member of a team of about ten developers whose objective is to create new applications, evolve and improve existing applications, and maintain existing projects. Given that we work on a large application scope, the technologies used are very diverse.

Summary: For this project, I am part of a team of 8 developers + tech lead working on a backend application for processing market instructions. This application has very important reliability and availability requirements, which translates into specific and high technical choices and testing constraints. The functionalities developed were primarily using the most used frameworks in the industry and Spring in particular.

Important point: each developer here is responsible for an end-to-end feature, from refinement to testing, delivery, and support; Quality is ensured through the use of Sonar, peer reviews, test coverage requirements, and the team members' experience level.

Role, responsibilities, technologies:

• Development and delivery of end-to-end user stories (dev to prod)

• Responsibility for the quality of the deliverable within the scope of responsibility

• Maintenance and adherence to Qualimetry standards

• Continuous improvement of the existing codebase

• Participation in agile ceremonies

• Java 19

• Spring Boot 3

• Spring framework version 5.3

• Spring Security 5.3 / Oauth2

• Spring Data JPA 3.0.5

• Spring AOP 5.3

• Spring WebFlux 5.2

• Backend systems architecture (JAVA). V2

• Mockito 5.0.0

• Junit 5

• Jenkins

• Kubernetes (AKS)

• Docker

Example tasks: Development of user stories in accordance with agile practices, unit tests with Junit/Mockito, code reviews, Kubernetes environment configuration (Lens), bug/hotfix analysis, implementation of OAuth2 authorization/authentication with Spring Security, continuous improvement.

Summary: For this project, I had various technical functions. I had the opportunity to be a proposer in a context where business demand is high and requires great reactivity. I also had the opportunity to work for the team in charge of the credit granting management engine (based on a rule management engine called Blaze). My responsibility in the team was to implement the new technical stack, integrate the application into the bank's environment, monitor and ensure the quality of developments, and also provide corresponding reports (Goprod ceremonies, etc.).

Core technologies: SpringBoot, Angular, RxJs, MobX, JAXWS, Docker, Tanzu, MapStruct, Spring security, Spring Test, Spring Data, FluxCD, Helm.

Role, responsibilities, technologies:

• Implementation of a CI/CD pipeline (FluxCD, HelmOperator, Docker, Jenkins, Sonar)

• Implementation of an existing improvement cycle, an example being the implementation of a delivery pipeline between the source manager and the development environment or the update of the Framework used by the API exposing components (to SpringBoot)

• Evolution and improvement of the mediation application (exposing an API produced by SpringBoot and managed by Kubernetes) within the framework of "continuous improvement" SaFe.

• Java 17

• Spring Boot 3

• Spring framework version 5.3

• Junit 5

• Angular

• RxJs

• Mockito

• Helm / Helm, Helm Operator,

• FluxCD 1.25.4

• JEE, JAX-RS, JAX-WS, SQL

• Environments: Tomcat, Tanzu, OpenShift, WildFly

• Jenkins Example tasks: Environment configuration for implementing GitOps practices (Git, Jenkinsfile), code review, improvement of the existing application architecture to facilitate development, securing a legacy application (encryption of confidential data), application refactoring for migration (JEE->Openshift JEE>Springboot)