Talk write-up: How to build a PaaS for 1500 engineers

I really enjoyed that write up. The focus on a good UI/UX in platform teams is definitely something that resonates with me. I also really liked the article placing an emphasis on Platform teams providing value by having a better "glue" I thought was interesting. I hadn't really thought that glue could be a component where value could be added. I really like the pattern of tools like "Devhose" and in developing a tool specifically to be the glue that integrates well with other tools.

I just want to note that in house platform can also be a big cost savers vs public clouds.<p>For example, you should be able to be 10x cheaper on GPU compute if you use consumer GPUs in-house.<p>From a conversation that I had with an academic IT person, he managed to save 2M$ yearly.

Stateless is the easy part, where are the databases?

Spot on!<p>Resonates very well with me, working at a scale up in a &quot;platform team&quot;.<p>Business wise we&#x27;re set to out engineer competition. Biggest challenges are definitely to get engineers on board on training and transitioning into new &quot;cool&quot; technology. Should we help highly skilled advanced teams run fast or focus on getting everyone on board the cloud native train?

Nice write-up Galo! As an ex-Deliveriarian I really enjoyed working this way, and the timing is perfect as I’m trying to set up a similar but way smaller PaaS. I’ll be borrowing this text :D

as a one person platform team (bare metal cluster + hpc resources); this article while super impressive gave me a kind of anxiety attack. I can barely keep the fires out and geez, look how much better it could be. There&#x27;s hope for some at least.

Built in tracking for the Accelerate metrics is awesome! Kudos