Rôles et Impact de Capgemini

Microservices & Cloud Computing - Course Introduction

• The course, "Microservices & Cloud Computing", is offered by Capgemini at ESIEA - 4a.
• The course duration is from 20/11/2024 to 21/11/2024.
• The course will cover various cloud concepts.

Agenda

• The agenda includes four presentations about cloud concepts.
• Presentation 1: Introduction to Information Systems (SI).
• Presentation 2: Microservices & Cloud Computing.
• Presentation 3: Cloud Architectures.
• Presentation 4: Cloud Scalability.

Agenda (Microservices segment)

• The agenda for the Microservices section includes:
  • Introduction to Microservices
  • Essential Microservices Patterns
  • Securing Microservices
  • Deploying and Maintaining Microservices
  • Logging
  • Monitoring
  • Introduction to Cloud Computing

Capgemini Overview

• Capgemini is a global leader in partnering with companies to transform and manage their business through technology.
• The company has more than 360,000 team members across over 50 countries.
• Capgemini is committed to unlocking the true value of technology for businesses, people, and society for a more inclusive, sustainable future.

JT: Professional Background

• JT holds a degree in Mathematics, specializing in fundamental mathematics, from the University of Avignon.
• JT also holds a Master's in Mathematics with a focus on Data Mining and Operational Research from the University of Aix-Marseille.
• JT has experience in software development (4 years), including roles as a data scientist.
• JT worked for 3 years in an IT services company (ESN) and had roles in the Spatial-Defense industry.
• JT has worked at Capgemini Financial Services for 8 years, focusing on architecture solutions, including Team Lead roles.

TD: Professional Background

• TD has a Bachelor's degree in Information and Communication Technologies from the University of Orleans.
• TD has a Master's degree in Applied Computer Methods for Business Management, with a focus on Distributed Networks, from the University of Orleans.
• TD has worked at Capgemini in a series of roles, including developer, team lead, and project manager.
• TD's experience includes roles in various industries such as application developments and financial services.

KN: Professional Background

• KN has a Master's degree in Biotechnological Engineering and Agro-industry Management from the University of La Rochelle.
• KN has experience in agro-industrial production management (2 years), developed expertise in Java development, API management, and architecture (6 years at Capgemini Financial Services).

TD & KN: Roles

• TD's Role as an architect involves defining solutions and guiding teams, technical lead tasks concerning architecture, and knowledge sharing.
• KN's Role includes defining solutions and working with teams, architecture lead roles, and supporting teams.

Monoliths & Microservices

• Monoliths are single-tiered software applications.
• Benefits include deployment ease and managed complexity.
• Limitations can include costly scalability issues and challenges in continuous deployment and rollback procedures.

Microservice Definition

• A Microservice implements distinct features or functionalities.
• Properties include modularity, autonomy (independent services for development and deployment), and data decentralization (individual databases).

Microservice Benefits

• Scalability (only needed resources are scaled),
• Faster development (due to small, independent services),
• Enhanced optimization (allowing multiple languages), and Fault isolation (failures don't halt the whole application).

Decentralized Architecture Governance & Catalog

• The shift toward decentralized governance in microservices is explained as compared to monoliths.
• The Service Catalog is a repository for available services making it easier for teams to discover, reuse and monitor services.
• Microservices architectures are more complex than monoliths with proper cataloging being important.
• In distributed transactions that span multiple services, rollback procedures can present challenges. Important considerations for End-to-End management, testing and monitoring are highlighted.

Notable Example: Netflix with AWS

• Discusses design patterns employed in Netflix's microservices architecture.
• Addresses limitations in the choice of monolithic architectures in applications, such as those found in the Netflix DVD Data Center architecture.
• Describes how techniques like Network Latency mitigation were crucial in avoiding cascading failures and bottlenecks.

DDD (Domain-Driven Design)

• DDD focuses on aligning software design with core business domains.
• It emphasizes collaboration with domain experts to establish a Shared Language model representing business concepts and rules.
• Subdomains and Bounded Contexts are used to divide complex systems for enhanced flexibility and scalability. A Ubiquitous Language is crucial for effective communication and understanding within the development team and with the business domain experts..

Circuit Breaker

• Circuit Breaker is a design pattern to prevent cascading failures.
• An 'open' circuit stops requests to the impacted service during temporary periods of instability, then resumes requests to that service once the circuit is closed.
• Popular implementations include Hystrix, Resilience4J and spring for resilience and fault handling.
• Demonstrates how to manage errors and prevent them from having wider cascading effects.

Retry Pattern

• Strategies for implementing retry mechanisms.
• Fixed Delay strategy with a constant retry interval.
• Incremental Delay strategy with an increasing retry delay.
• Exponential Backoff strategy with an exponential increase in retry delay.
• Used for handling transient errors or failures.

Event Broker Pattern

• Describes the event broker pattern in software architecture.
• Key features for Event Routing, scalability and loose coupling are mentioned.
• Enables asynchronous, event-driven communication, enabling system flexibility and resilience.

Authentication vs. Authorization

• Authentication verifies the user's identity.
• Authorization defines permitted actions.
• Authentication typically precedes authorization to access network resources.

SSO (Single Sign-On) & JWT Patterns

• Single Sign-On approach allows users access to multiple applications.
• OAuth protocol allows third-party access limited to user resources.
• OIDC protocol is a layer built on top of OAuth, adding identity verification and access profile information.

OAuth Pattern

• Steps involved in the OAuth process, including user login requests, granting permissions and receiving access tokens for authorized access.

OIDC Pattern

• Steps involved in the OIDC process including user interaction with the IdP (Identity Provider), and acquiring and verifying access tokens and security tokens.

Monitoring Tools

• Grafana, Splunk are open-source software for data viz and monitoring.
• Allow using various data sources for real-time observability and performance tracking.

Importance of CI/CD and DevOps

• CI/CD pipelines consist of several stages including planning, design, coding, compilation testing, and publishing to deployment environments.
• Automation is crucial for agility in software projects, enabling quicker scaling and faster recovery from errors, and reducing downtime.

Simple and Complex CI/CD for Java Projects

• Various CI/CD pipelines are explained for Java projects, highlighting different approaches for source code management automation.
• Simple pipelines include tools like Jenkins, Dockerized deployments and testing.
• Complex CI/CD pipelines used by banks include more configuration and integrations to multiple environments and processes, in order to manage larger projects with significant integration needs.

Cloud Service

• Describes aspects and characteristics that define a cloud service, such as demand-based IT services, automated deployments, scalability, and a pay-per-use model.

Differences between Non-Cloud and Cloud Projects

• Non-Cloud projects (Pets), involve unique, custom, and personalized components.
• Cloud projects (Cattle), involve standardized, replaceable components.

Liabilities (Cloud vs Client)

• This part highlights the shared responsibility model between the client and cloud providers with descriptions regarding various aspects of cloud services (authentication, access management, software configurations, and hardware infra).

Course Conclusion/Next Steps

• The presentation concludes, potentially with call to action requests for further inquiries, or references to next steps.
• Contact details and social media links for the instructors (Thomas Desrut, Kevin Navarri, Julien Trouillet).