2024-05-30_meetup_devops_aix-marseille.pdf

Slides de notre meetup DevOps AixMarseille du 30 mai 2024 chez SmarTribune

Sujets: platform engineering / terragrunt / test containers

1. Maker May - SmartTribune
Platform Engineering et
quickies
30/05/2024

2. Un grand merci à

3. Qui sommes-nous ?
Thomas Perelle
Freelance
Frédéric Léger
Emilien Escalle

4. I.Annonces
II.Smart Tribune
III.Platform Engineering
IV.Quickies (terragrunt & test containers)
V.Jeu + goodies
VI.Apéro / Buffet
Sommaire

5. 6/6/24 | WAX
https://www.waxconf.fr/

6. Ici vont les slides SmartTribune

7. Platform Engineering

8. Platform Engineering
Overview
Thomas Perelle

9. Definition of Platform Engineering
“Platform engineering is the discipline of designing and building toolchains and workflows that enable
self-service capabilities for software engineering organizations in the cloud-native era.
Platform engineers provide an integrated product most often referred to as an “Internal Developer Platform”
(IDP) covering the operational necessities of the entire lifecycle of an application.”
– Humanitec, What is platform engineering

10. Who am I?
Thomas Perelle
?????? Lead Platform Engineering - Freelance

♥ Transformation/Innovation projects and strategy
♥ Working in team and sharing knowledges
♥ Making things working better


@tperelle
@thomasperelle

11. Definition of Platform Engineering
“Platform engineering is the discipline of designing and building toolchains and workflows that enable
self-service capabilities for software engineering organizations in the cloud-native era.
Platform engineers provide an integrated product most often referred to as an “Internal Developer Platform”
(IDP) covering the operational necessities of the entire lifecycle of an application.”
– Humanitec, What is platform engineering

12. It’s always about organizational concerns

13. Trendy but not always essential
You don’t need it:
●Small team
●Few teams
●Few projects in parallel
●Good pace to deliver

KISS is always better when
possible!

14. When is it appropriate?
You encounter difficulties at scale:
●Federating a lot of development teams
●Ensuring compliance
●Managing technical debt
●Slow innovation
●Frictions between teams
●Unclear responsibility boundaries

The amount of trouble outweighs the
investment in getting organised!

15. Methodology landscape
Platform engineering does not
replace any other approach, it
complements what already exists!
●Lean
●Agile
●Scrum
●SAFe
●DevOps
●…

16. Lean management
Inspired from the Toyota Production System
(TPS) in the 90’s.

Eliminate waste that reduces the efficiency and
performance

17. Agile methodology
Describe in the Manifesto for Agile Software
Development written in 2001.

Fights against the high failure rate of software
development projects

18. Scaled Agile Framework (SAFe)
SAFe is a framework designed for large-scale
deployment of Agile and Lean methods.

Get several Agile teams working together at scale

19. DevOps
The DevOps movement appeared around 2007 with Patrick Debois.

Breaking the “wall of confusion” between DEV and OPS teams

20. What’s about platform engineering?
Answer frustration following DevOps adoption:
●High cognitive load in Dev teams
●Ops overwhelmed by tickets

21. Platform Engineering, concepts and terminology

22. Platform team
Team Topologies is a model for describing the organization of software
development teams

Related to the Conway’s law:
“Conway's law describes the link between communication structure of
organizations and the systems they design.” - Wikipedia

23. Platform team
Source: Building a successful platform team at
CROZ
Stream-aligned teams
●Own an entire slice of the business domain end-to-end
●“You Built It, You Run It” teams
●Outcome / Business oriented

Platform team or group
●May be a group of teams
●Provide an internal product to accelerate delivery by
Stream-aligned teams
●Reduce cognitive load

24. Improving Developer Experience is not the only objective
Platform Team
Executives
Product owners
Dev teams Ops teams
Security team
Other
Think holistically!

25. Platform team ≠ SRE
While SREs focus on the reliability of the production environment, platform
engineers focus on building an Internal Developer Platform to enable developer
self-service with low cognitive load.
SRE vs. DevOps vs. Platform Engineering: What’s The Difference?

26. The concept of “Platform”
Automotive manufacturers use the platform concept for a long
time:
●The first is General Motors in 1908!
●The platform sharing is common since 1960s

The concept of platform is widely used:
●Automotive
●E-commerce - Amazon, eBay, etc.
●Media - Facebook, Netflix, etc.
●IT - Cloud Platforms!
“Most definitions portray platforms as amplifier: they create
something bigger than just the sum of their parts.” - Gregor
Hohpe

27. Internal Developer Platform
Internal Developer Platform (IDP):
●Expose golden paths
●Hide complexity
●Many tech and tools glued together
○Requires multiple skills (dev, ops, cyber,
network, iam, etc.)
●Managed “as a Product”, not a project
Organization
Responsibility
boundaries
Templates
Golden paths
Well defined
processes
Portal
Self service
Skills
Documentation
Tooling

28. Internal Developer Portal
The Internal Developer Portal (IDP) is the interface
of the platform.
Key capabilities:
●Service catalog
●Dashboard
●Integrations
●Score cards
●Developer self-service
●RBAC
●Auto documentation

Source: https://humanitec.com/internal-developer-portal

29. Platform Orchestrators
CI/CD Pipelines and
triggers

30. IDP Architecture example

31. Golden path principles
The Cloud Native Computing Foundation
defines a Golden Path as a "templated
composition of well-integrated code and
capabilities for rapid project development." 
=> It is a self-service template for common
tasks
1.Provide a single, clear, opinionated method 
2.Reduce the cognitive load 
3.Integrate with existing internal developer platforms
4.Light the complete path from development to production
5.Be self-service
6.Provide a transparent abstraction
7.Address your organization's specific needs
8.Allow for flexibility
9.Be optional

32. Don’t build pyramids…
●Require to anticipate all user’s needs
●The build is more complex and expensive
●Avoid creativity and diversity
●Platform team holds responsibility
Allow building on top!
●Hide complexity
●Offer simple and ready-to-use interface
●Engage users
●Allow innovation to answer new needs
●Shared responsibility model

33. API Governance
APIs become a cross-functional and cross-technical
language, allowing both technical and business
stakeholders to communicate.
●Leverage existing APIs to offer transparent
integration in golden path
●Create your own APIs to provide additional services
or business-specific
●Use API specification format to ensure uniformity
across the organization: OpenAPI, AsyncAPI or AWS
RAM for example
●Share and reuse Data Object Schemas to avoid
having multiple representations for a same thing
●Communicate about the API ecosystem and
governance rules (self-service portal, documentation,
talks, etc…)

Generated with Midjourney

34. Platform tooling landscape
https://platformengineering.org/platform-tooling

35. Advices and reminders

36. Getting organised costs money

37. Change organization requires strong
sponsorship

38. A bad organization can also disorganized

39. Don’t forget change management

40. Customer onboarding and support are
very expensive

41. Without a positive return on investment of the
platform engineering initiative within the first 12
months - the initiative does not deserve to survive

42. Resources to go further
●Internal Developer Platform
●Platform Engineering blog - Humanitec
●Platform as a product
●How to build a Minimum Viable Product (MVP)
●Why putting a pane of glass on a pile of sh*t doesn’t solve your
problem
●Platform Orchestrator: the Platform Engineering game changer

PlatformCon 2024 - 10-14 June 2024
Platform Engineering Community

43. Thank you!

Any questions ?

44. Quickies

45. Terragrunt
●Gruntwork (terragrunt.gruntwork.io)
●Une autre façon de gérer du multi environnement avec terraform
●Plus facile de gérer les dépendances entre modules / ressources
●Approche basée sur les modules terraform
●Pas mal de fonctions et hooks pratiques

46. Terragrunt

47. Terragrunt

48. Testcontainers

Testcontainers est un framework open source permettant de fournir des instances légères et jetables de
bases de données, de brokers de messages, de navigateurs web ou de tout ce qui peut fonctionner dans un
conteneur Docker.
https://testcontainers.com/

49. Differences with Docker and Docker Compose
Docker and Docker Compose approach has downsides.
-It may result in port conflicts,
-Containers not being fully initialized or ready for interactions when the tests start, etc.
Testcontainers libraries leverage the full power of Docker containers under the hood and expose them to
developers via idiomatic APIs.

50. Testcontainers workflow

51. Configuration

52. DevOps needs you !
●Speakers pour les prochains meetups
●Volontaires
Oui nide iou !

53. meetup.com/Devops-Aix-Marseille
ibd.sh/openbar

54. Quizz !!

55. Apéro