How Platform Engineering Compares to Running a Restaurant

Dive into the fascinating world of platform engineering while we draw parallels between the complex operations of a bustling eatery and the intricate processes of platform engineering. Just as a successful restaurant relies on a harmonious blend of ingredients, staff, and ambiance to delight customers, platform engineering integrates various technologies, teams, and practices to deliver robust software solutions. Join us as we explore the similarities in skill sets in both fields.

▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬
Sponsor: DoubleCloud
Save time & costs by streamlining data pipelines with zero-maintenance open-source solutions. From ingestion to visualization: all integrated, fully managed, and highly reliable, so your engineers will love working with data.
▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬

#PlatformEngineering #InternalDeveloperPlatform #IDP

▬▬▬▬▬▬ 💰 Sponsorships 💰 ▬▬▬▬▬▬

▬▬▬▬▬▬ 👋 Contact me 👋 ▬▬▬▬▬▬

▬▬▬▬▬▬ 🚀 Other Channels 🚀 ▬▬▬▬▬▬

▬▬▬▬▬▬ ⏱ Timecodes ⏱ ▬▬▬▬▬▬
00:00 Platform Engineering vs. Restaurant
01:54 DoubleCloud (sponsor)
02:54 Platform Engineering vs. Restaurant (cont.)

[nelloserio]

Great explaination, as always! This simplified analogy between restaurant and IDP becomes extremely useful for those who needs to have a high level idea about what an IDP is and what added values brings to the company productivity, while still hiding the complexity and the necessary integrations to implement a solid solution. The Waiter example clearly highlights the boundary that separates users point of view from the backend details
Keep it up! 💪🏼💯

[steve-at-yt]

I have been thinking about this many many times and you bring it to the point! Awesome!

[IvanRizzante]

Thank you for this video, I really liked the comparison between platform engineering and restaurants, it really clarifies the concepts behind it. I bet that while many people already know how to implement the other parts (service catalog, services, ...) at least up to a certain point it's still unclear how to get the feedback part done right. Maybe it could be an idea for an upcoming video?

[VagharshakBaghdasaryan]

@DevOpsToolkit. Great mental model of Platform Engineering - thanks a lot for this! In this mental model, and in your opinion, would be a YAML file a proper API for stream aligned teams to "order" things from Platform engineering? (like a simple definition of a Hosted Zone in AWS, defined as custom YAML and parsed / processed from some Platform Engineering tool).

And, again, would it fit the restaurant mental model, if developers define this 2-4 lines in YAML by themselves and create a PR for that, which will be reviewed and merged afterwards by Platform Engineering team?. Or are we speaking about a Platform only, if we have a UI for devs or kind of CLI for "ordering" things, without the need for devs to write code (even if it is a simple YAML) and create a PR?

[michaeljuliano]

One thing I’ve been a bit confused about is how GitOps practices interact with this kind of platform. When you provide your users with an API to order their own infrastructure, would the API be interacting with a git repo, or is this a different thing that falls outside the scope of GitOps?

[MrEvgheniDev]

Greate compare, thank you! Interesting who is sommelier in this restaurant?

[Yair-wjir]

Hi, great video, i didnt understand the part about observability, how can one filter and transform the logs (technically) which frameworks recommend? Also how would one expect the logs to be?

[DerJoe]

Very nice comparison and very well explained!
Is there a simple tool for creating menus from APIs, besides kubectl explain or IDE's Kubernetes plugin (which are great but kinda "low level")?

[sredevopsorg]

I've spent years of literal pain, suffering and stress until I've realized that I wasn't the problem, just -at most- a minor part of the problem when it comes to culture, management and horrible practices, even if we don't take in count the poor ownership/governance which it's seems to be a "global pandemic" hahahaha, regards from Chile!