Cloud Services and Capgemini Overview

Microservices & Cloud Computing

• Topics covered include: Introduction to Systems, Microservices & Cloud Computing, Cloud Architecture, Cloud Scalability, and an agenda of presentations.
• This is a Capgemini course (20/11/2024 - 21/11/2024) for ESIEA - 4a students.
• The agenda includes topics on: Introduction to Microservices including Essential Patterns, Securing Microservices, Deploying/Maintaining Microservices, Logging, Monitoring, and Introduction to Cloud Computing.

Agenda

• There are 4 presentations on Cloud Concepts.
• The presentations include: Introduction to Systems, Microservices & Cloud Computing, Cloud Architecture, and Cloud Scalability.

Agenda - Microservices & Cloud Computing

• Presentation about Introduction to Microservices.
• Presentation about Essential Microservices Patterns.
• Presentation about Securing Microservices.
• Presentation about Deploying and Maintaining Microservices.
• Presentation about Logging.
• Presentation about Monitoring.
• Presentation about Introduction to Cloud Computing.

About Capgemini

• Capgemini is a global leader partnering with companies to transform and manage their business, using technology.
• Their purpose is to unleash human energy through technology for an inclusive and sustainable future.
• They have over 360,000 team members in more than 50 countries.
• They leverage cloud, data, AI, connectivity, software, digital engineering, and platforms to address a wide range of business needs, reflecting a commitment to inclusive and sustainable future.
• In 2022, their global revenue was €22 billion.

Mon Parcours - JT

• Has a Bachelor's degree in Mathematics.
• Master's degree in Mathematics from the University of Aix-Marseille related to Data-Mining & Operational Research.
• 4 years in a start-up software company as data scientist, working with JAVA and R.
• 3 years as a software Engineer in a large Engineering company for space defence industry, using JAVA, Matlab, and R.
• Currently with Capgemini Financial Services for 8 years as an architect, Team Lead, and Solution Architect.

Mon Rôle - JT

• Defines business requirements and solutions.
• Defines architecture for solutions.
• Teams' leader, and technical coordinator.
• Consultant/Manager at Capgemini.
• Responsible for creating and maintaining different roles.

Mon Parcours - TD

• Bachelor's Degree in Information and Communication Technology from the University of Orléans.
• Master's degree in Applied Computer Science for Business Management, specialising in Distributed Networks from the University of Orléans.
• 6 years working for Capgemini Apps as a developer.
• 3 years at Capgemini as a Team Lead, Project Manager.
• 5 years at Capgemini Financial Services, as a Solution Architect.

Mon Rôle - TD

• Defines business needs and outlines solution architecture.
• Translates architectural visions into technical components.
• Technical Lead for Architecture.
• Consultant/Manager at Capgemini.

Mon Parcours - KN

• Master's Degree in Biotechnological Engineering and Agro-industry Management from the University of La Rochelle.
• Has a background in agro-industry.
• 2 years as a Production Manager in an agro-industry.
• 6 years at Capgemini Financial Services as a Java developer, experienced in API Management, and architecture.

Monothlits and Their Limitations

• Monolithic application: Single-tiered software application. Different modules combined into one program.
  • Easy to deploy and test.
  • Managed complexity and centralized services.
  • Low dependency on shared infrastructure.
  • Limitations: Scaling challenges, high cost, and long update delays.
  • Difficult to update specific features without updating the whole system.

Definition and Properties of a Microservice

• A microservice implements a set of functions.
• Modular structure: Each microservice focuses on specific business functions.
• Autonomous and independent: Allows flexibility in development and deployment.
• Decentralized data model: Each service has its own database for data isolation.

Benefits of Microservices

• Scalability: Ability to scale only necessary resources.
• Development Speed: Independently deployable microservices allowing for faster deployment.
• Optimization/Compatibility: Enables multi-language use for optimum performance.
• Fault Isolation: Service failures do not impact the entire application.

"Decentralized" Architecture: Governance & Catalog

• Shift from centralized to decentralized governance in microservices.
• Managing per-service governance, using a schedule & roadmap.
• Using the Service Catalog as a repository helps teams in discovering, reusing, and monitoring services.
• Complex microservice architecture, proper cataloging is pivotal.
• Distributed transactions require synchronization for various rollback scenarios.

Notable Example: Netflix with AWS

• Netflix uses AWS microservices architecture.
• Lock in massive databases.
• Javaweb implementation.
• Difficult to diagnose issues due to multiple code and base changes.
• Network latency and congestion issues.
• Difficult scaling leads to failures.
• Edge, Middle Tier, and Platform are key components of their structure.

Business-Driven Orientation : What is DDD

• Domain-Driven Design (DDD): Aligns software design with business domain.
• Emphasizes collaboration with domain experts to create a shared language.
• Ubiquitous language: Used across different areas of the project or organization. Enhances efficiency.

Business-Driven Orientation: What is DDD

• Dividing complex systems into subdomains and bounded contexts for flexible and scalable applications.
• Connects software solutions closely to business needs.
• Creating a shared language and model to represent business concepts, enabling more effectively designing, implementing, and managing software applications.

Circuit Breaker

• A design pattern to prevent cascading failures in a distributed system.
• When a service fails repeatedly, the circuit opens and stops requests.
• Popular implementations include Hystrix, Resilience4j, and Spring.
• When stable, the circuit closes and resumes normal operations.
• Helps improve system resilience by stopping cascading failures.

Retry Pattern

• Strategies for implementing retry mechanisms in software applications.
  • Fixed delay: Sends retry requests after a fixed time interval.
  • Incremental delay: Increases delay with each subsequent retry.
  • Exponential back-off: Exponentially increases delay for subsequent requests.

Event Broker Pattern

• Manages and distributes events between producers and consumers (publishers/subscribers).
• Event routing: Directs events to the appropriate consumers based on predefined rules.
• Scalable system: Allows multiple consumers to process events concurrently.
• Loose coupling: Producers and consumers don't need to know each other directly.

Authentication vs. Authorization

• Authentication: Verifying user identity using credentials (tokens, passwords, biometrics).
• Authorization: Determining access privileges and actions allowed for an authenticated user.

SSO and JWT Patterns

• SSO (Single Sign-On): Enables users to log in once and access multiple applications without re-authentication.
• OAuth 2.0: Authorization protocol giving third-party apps limited access to user resources.
• OIDC (OpenID Connect): An identity layer built on OAuth 2.0, focusing on verifying user identity and access profile information.

OAuth Pattern

• User logs into an application through an authorization server.
• Authorization server asks user if they consent to share resources.
• Third party receives authorization token and use it to gain access to user resources.

OIDC

• Request users to access application via identity provider.
• IdP (identity provider) verifies details.
• Approves client access.
• Grants or denies access, based on security protocols.
• Returns security tokens.
• Application uses token to grant access back to end user.

Importance of CI/CD and DevOps

• Automation of processes to enhance software development.
• Collaboration among developers, testers, and operators involved within the pipeline.
• Automation steps include planning, coding, compilations, testing, and publishing and deployment processes.

Simple and Complex CI/CD for a Java project & Bank

• Tools used in the Continuous Integration and Continuous Delivery (CI/CD) pipelines, such as Jenkins, and Bitbucket.
• Steps include code repository, compilation, automated testing, and deployment.
• Example of CI/CD pipelines for a banking application, and associated challenges.
• Software tools and procedures used, such as Jenkins and Orchestrator, are employed to manage the entire workflow.

Centralized Logging Tools (ELK Stack)

• Centralized logging tools like ELK Stack (Elasticsearch, Logstash, Kibana).
• Aggregating logs across different services.
• ELK Stack components include Logstash for processing, Elasticsearch for storage, and Kibana for visualisation.

Importance of Logs for Diagnostics and Issue Resolution

• Shows a range of log entries and their usefulness for resolving incidents.
• Demonstrates the importance of logging and monitoring application behaviours.
• Using correlation ID to identify specific transactions through complex environments.
• Tools like ELK assist in efficiently searching and analysing vast logging data.

Introduction to Monitoring Tools (Prometheus, Grafana, Splunk)

• Grafana: Open source tool for data visualization.
• Splunk: A platform for data analytics, indexing and visualization; used for monitoring business intelligence.

Importance of Observability: Metrics, Alerts, Performance Tracking

• Monitoring system performance through metrics, alerts, and tracking.
• Data visualization tools showing key metrics like resource utilization.
• Real-time data analysis from graphs and charts used in observability.

A Cloud Service

• On-Demand IT Services.
• Automated Deployment.
• Allowing Elasticity in computing resources.
• Pay-per-Use cost model.

Differences Between Non-Cloud and Cloud Projects

• Non-Cloud projects (Pets): Unique, individualized management style.
• Cloud projects (Cattle): Standardized approach to management; scalable, replaceable.

Liabilities (Cloud vs. Client)

• Cloud provider responsibility: Infrastructure security, network, and global infrastructure.
• Client responsibility: Data encryption, authentication, and security in the cloud environment.
• AWS services used for managing and computing resources in the cloud.

Introduction to Cloud Computing

• Different cloud types including public cloud, private cloud, and hybrid cloud.
• Deployment models (IAAS, PaaS, SaaS).
• Service provider manages infrastructure/servers. Cloud provides scalability and flexibility. Cloud providers manage the infrastructure, security, and availability.
• Regions and Availability zones. Cloud locations and dedicated appliances.
• On-demand access to resources reduces hardware costs.

Test your knowledge on cloud services, their characteristics, and Capgemini's approach to technology and business transformation. This quiz covers key concepts such as elasticity, caching benefits, and the pay-per-use model. Perfect for anyone looking to deepen their understanding of cloud computing and Capgemini's mission.