Logging et Authentification avec ELK Stack et OIDC

Microservices & Cloud Computing Course

• Dates: November 20/2024 - 21/2024
• Location: ESIEA - 4a
• Presenters: Kevin Navarri, Thomas Desrut, Julien Trouillet
• Course Content: The course will cover several presentations concerning cloud concepts, including:
  • Introduction to Information Systems (SI)
  • Microservices & Cloud Computing
  • Cloud Architecture
  • Cloud Scalability

Agenda

• Agenda (Day 1 & 2): Introduction to Microservices, Essential Microservices Patterns, Securing Microservices, Deploying and Maintaining Microservices, Logging, Monitoring, Introduction to Cloud Computing

Agenda (Detailed)

• Day 1 & 2 Topics:
  • About Us (overview of the presenters and Capgemini)
  • Introduction to Microservices (fundamental concepts and definitions)
  • Essential Microservices Patterns
  • Securing Microservices
  • Deploying and Maintaining Microservices
  • Logging
  • Monitoring
  • Cloud Computing Introduction

Capgemini Profile

• Global Leader: Capgemini partners with companies to transform and manage their businesses using technology, aiming for an inclusive and sustainable future.
• Responsible & Diverse: More than 360,000 team members in over 50 countries leverage cloud, data, AI, connectivity, software, etc.

Architectes' and Engineers' Career Paths:

• JT (Julien Trouillet) :

  • Education: Licence Mathématiques parcours mathématiques fondamentales, Université d'Avignon / Master Mathématiques : Data-Mining & Recherche Opérationnelle, Université d'Aix-Marseille
  • Experience: 4 years in a start-up (data scientist - Java, R) / 3 years in an ESN (Engineer R&D, spatial defence sector - Java, Matlab, R)
  • Current role: 8 years at Capgemini Financial Services (architect solution / team lead)

• TD (Thomas Desrut) :

  • Education: Licence Sciences et Technologies de l'Information et de la Communication, Université d'Orléans / Master Méthodes Informatiques Appliquées à la Gestion d'Entreprise, spécialité Réseaux Distribués, Université d'Orléans
  • Experience: (6+ years) at Capgemini Apps - (3+ years) at Capgemini Per - (5+ years) at Capgemini Financial Services (architect solution/team lead)

• KN (Kevin Navarri) :

  • Education: Master Génie Biotechnologique et management en agro-industries, Université de La Rochelle
  • Experience: (2 years) in agro-industry production / (6+ years) at Capgemini Financial Services (developer Java, API Management, architecture applicative)

Roles & Responsibilities (Examples)

• JT Role: Architect Solution / Architect Functionnel / Team Lead / Technical Coordinator/ Consultant/ Manager Capgemini
• TD Role: Architect Solution / Architect Functionnel / Technical Lead (architecture applicative)

Monoliths and Microservices

• Monoliths : Single-tiered software, combining modules into a single program.

  • Benefits: Easy Deployment, Managed Complexity, Low Dependency
  • Limitations: Expensive Scalability, Low Update Frequency, Issues with Rollbacks

• Microservices : Implement discrete functionalities, each being a mini-application.

  • Properties: Modularity (specific business functions), Autonomy (independent development and deployment), Data Decentralization (each microservice typically has its own database).
  • Benefits: Scalability, Faster Development, Fault Isoliation

CI/CD and DevOps

• CI/CD (Continuous Integration/Continuous Deployment) and DevOps:
• Key stages: plan, design, development, feedback, release, test, deploy and operate
• Tools frequently used with DevOps, and CI/CD Jenkins, Bitrise, Kubernetes, Docker, Github, SonarQube

Logging

• Importance: Crucial for diagnostics and problem resolution.
• Tools: Centralized tools like ELK Stack (Elasticsearch, Logstash, Kibana) are frequently used.

Monitoring

• Importance: Real-time observability for performance tracking and issue detection.
• Tools: Grafana, Splunk are used for dashboards, visualization and analysis.
• Metrics: Essential for performance monitoring. Examples: CPU usage, memory usage, traffic rates.

Cloud Computing (Public, Private, Hybrid)

• Public Cloud: Services provided by a third-party provider, typically on a pay-per-use basis.
• Private Cloud: A dedicated cloud environment controlled by a single organization.
• Hybrid Cloud: A combination of on-premises and cloud environments for flexibility.
• IaaS, PaaS, SaaS: Different cloud service models (Infrastructure as a Service, Platform as a Service, Software as a Service).

Differences between Non-Cloud & Cloud Projects

• Non-Cloud (Pets): Unique, highly specific, and well-maintained.
• Cloud (Cattle): Many instances, standardized, easily replaced.

Liabilities (Cloud vs. Client)

• Customer Responsibility: Security in the cloud (client-side data encryption, authentication procedures)
• Cloud Provider Responsibility: Security of the cloud (infrastructure, platform, network)

Security

• Authentication: Verifying a user's identity (e.g., using passwords).
• Authorization: Determining a user's permissions (e.g., access to particular resources).
• SSO (Single Sign-On): Enables single login for multiple applications.
• OAuth, OIDC: Authorization standards that enable third-party applications to access user data without exposing credentials.

Patterns (e.g. OAuth & OIDC).

• OAuth, OIDC use cases: Secure access, protect user’s data, implement single sign-ons.

Microservice-Design: Design Patterns and implementation steps to create microservices :

• Event broker Pattern : (asynchronous communication between producer and consumers; decoupled components).
• Retry pattern - strategy for when a client or service fails to respond within a timeout
• Circuit breaker pattern – stops a broken or unstable service to avoid cascading failures.

Key takeaways for future learning:

• There is an emphasis on data visualization and analysis (dashboarding).
• The shared language use is a key concept.