Mounaim L.

New solution to provide the BNP group's cloud offerings:

The objective of this project is to create a new solution to provide the group's cloud offerings.

- Reduce the creation time of a cloud resource (compared to the old solution)

- Develop pilot cloud offerings to validate the architecture solution.

Responsibilities:

- Participation in the implementation of the architecture.

- Creation of Terraform providers with Go that are specific to the group

- Creation of a modular Terraform structure reusable for sharing among the proposed cloud offerings

- Implementation of micro-services (with Java 17, Spring Boot 3.0.6, Spring Cloud)

Technical Environment: HELM3, Kubernetes, IBM Cloud, Hvault

Project: Migration of applications to a new Kubernetes infrastructure

Before, our applications were hosted in a Kubernetes environment with on-premise VMs, and the objective of this project is to move these applications to a managed IBM cluster

- Adapt Kubernetes deployments to the new environment

- Transition to Helm for deployments

Responsibilities:

- Preparation of a migration plan without service interruption.

- Preparation of traffic routing

- Preparation of the Helm chart

Technical Environment: HELM3, Kubernetes, IBM Cloud, Hvault

Project: Hybrid Cloud BNP

This is a project in partnership with IBM to create the group's cloud offerings while respecting BP2I standards:

- Creation of a VSI offering (to order virtual servers)

- Creation of VIP/LB offerings (Virtual IP server/Load Balancing)

- Microservices architecture + BPM (IBM orchestrator) + low-level layers to manage infrastructure operations

- Authentication based on OAuth 2.0 (keycloak) across the entire system.

Responsibilities:

- Design of cloud offerings with product owners.

- Technical referent for the team: implementation of best practices for microservices layers, and REST API exposure.

- Migration of the technical foundation of the entire self-service bike system

This project aims to upgrade all system microservices to Java 11 / Spring Boot 2 with all compatible frameworks and the company's low-level frameworks, which represent the common part of the microservices:

- Migration from Java 8 to Java 11

- Migration from Resteasy to Jersey.

- Netty server to Apache Tomcat server

Responsibilities:

- Technical referent for the team: implementation of best practices, review of actions taken by the team (merge requests).

- Technical unblocking of development team members.

- Creation of POCs for technical component migrations.

- Documentation of migrations

Technical Environment:

- Backend: Java (8/11), Spring Boot (1.5/2.2), Spring MVC, Spring Data, Spring Actuator, Micrometer, JAX-RS, Jersey, Rest Easy, Git, GitLab, Quartz, Maven, Mockito, Lombok, Liquibase, Flyway, PostgreSql, InfluxDB, Elasticsearch, Grafana, Dynatrace.

Code and delivery management: Git flow, merge requests.

- Industrialization and deployment:

- Jenkins, Ansible.

System that provides bikes to the public with different offers and is available on various platforms (mobile, web, kiosks):

- Microservices architecture + a legacy part of the system.

- RESTFUL APIs with a versioning strategy and backward compatibility.

- Authentication based on OAuth 2.0 across the entire system.

Responsibilities:

- Estimation and development of User Stories and Technical Stories.

- Ensure the implementation of good development practices.

- Maintenance and evolution of low-level internal frameworks.

- Technical unblocking of development team members.

- Analysis of production incidents with the team and implementation of quick fixes (hotfixes).

- Participation in front-end development and coordination between front-end and back-end topics.

Team composition: Feature team of 4 developers (2 backend and 1 frontend and 1 mobile), Scrum Master, 1 transverse software architect, 1 Product Owner, 1 business analyst.

Technical Environment:

- Backend: Java (8/11), Spring Boot (1.5/2.2), Spring MVC, Spring Data, Spring Actuator, Micrometer, JAX-RS, Jersey, Rest Easy, Git, GitLab, Quartz, Maven, Mockito, Lombok, Liquibase, Flyway, PostgreSql, InfluxDB, Elasticsearch, Grafana, Dynatrace. Frontend: Angular 6.

- Code and delivery management: Git flow, merge requests.

- Industrialization and deployment:

- Jenkins, Ansible.

- Git flow, Git, Sonar, Nexus.

Project: SHINE2 - Orange France DSI [BUILD Project]

- SHINE2 was designed to foster open innovation at Orange with external stakeholders (startups, clients) by providing external APIs to integrate with services offered by Orange partners, with the goal of offering them to clients through Orange.

Responsibilities:

- Development of backend User Stories and Technical Stories.

- Development of User Stories.

- Responsible for code quality and the implementation of security best practices for APIs.

- Technical unblocking of development team members.

- Handling of application performance and deployment infrastructure issues in collaboration with the software architect.

Technical Environment:

- JAVA JEE, Spring Cloud (Zuul, Eureka), JWT, Spring Boot, Spring IOC, REST, Spring JPA Repository, Cloud Foundry, Angular 5

- Industrialization: Maven, Git, Sonar, Gitlab, Nexus, Cucumber/Junit, ZAP.

Project: Orange Delivery Orchestration Application - OLIV - Orange France DSI [BUILD Project]

An order and/or delivery API between internal or external Orange partners with a console for error management and other options for application support.

The API allows orchestrating network access and accessory orders. To perform these operations, we interface with various Orange systems for activation/deactivation of billing, activation/deactivation of network parameters, reservation of call numbers, suspension of a line, etc.

Interfacing with internal Orange systems:

- Call number reservation/release system (MSISDN)

- Number release system.

- Orange billing system (to activate or deactivate billing for network access).

- Network options activation system (CFS: VOICEMAIL, MOBILEACCESS).

Responsibilities:

- Estimation and development of User Stories and Technical Stories.

- Maintenance and creation of Jenkins jobs.

- Analysis and diagnosis of production malfunctions.

- Evolution of a utility application that allows launching a set of mocks for the different systems with which we interact.

- Responsible for code quality and the implementation of security best practices for APIs.

- Technical unblocking of development team members.

- Handling of application performance and deployment infrastructure issues in collaboration with the software architect.

- Scrum Master for the team:

◦ Ensure the smooth running of sprints: Propose solutions in cases of ambiguity on US or technical blockages/limitations.

◦ Facilitate Sprint meetings (Daily meeting, Sprint Planning, Sprint Review, Sprint Retrospective).

◦ Follow up on Retrospective actions.

Team composition: 5 developers (3 experienced and 2 junior), 1 Technical Lead / Scrum Master, 1 Software Architect, 1 Product Owner, 1 Project Manager.

Technical Environment:

- JAVA JEE, Spring REST, Spring Boot, Spring IOC, Hibernate, Apache CXF, CFT.

- Shell Scripting

◦ Shell scripts run during Jenkins builds for file replacement and server configuration operations.

- Industrialization:

◦ Maven (maven-surefire-plugin, maven-antrun-plugin): Creation of profiles, integration of Maven phases for test execution, Sonar analysis, and report publication.

◦ Git, Sonar, Jenkins, Nexus, Cucumber/Junit, ZAP.

Project: Service Mesh [SHINE2] - Orange France DSI [BUILD Project]

The Shine project is designed to foster open innovation at Orange with external stakeholders (startups, clients) by providing external APIs to integrate with startup business applications without Orange development. The application also allows ordering equipment...