
Desertcart purchases this item on your behalf and handles shipping, customs, and support to Bolivia.
Developer platforms appear to be able to rewrite the laws of IT physics: they boost innovation by standardizing, speed up developers while assuring compliance, and reduce cognitive load without restricting choice. Sadly, many organizations who embark on this journey end up with renamed IT services, a thin veneer over public cloud services, or a rigid not-so-golden path instead. Needless to say, the magic of platforms wonโt materialize in such a setup. Harvested from a decade of building successful in-house platforms, this book reveals what makes IT platforms actually work. Youโll learn why successful platforms are more like a fruit salad than a fruit basket and float rather than submerge. Youโll discover why a thorough understanding of your organizationโs technical business domain is equally critical and lacking on platform teams, and why trying to anticipate all usersโ needs is a common mistake. The focus isnโt on adding to the long list of promises that platforms make, but on how to make those promises come true. Following the Architect Elevator concept, the book takes IT architects, executives, and engineers on a shared journey from positioning platforms in the context of IT strategy to defining success metrics, setting up platform teams, and making technical design trade-offs in real-life scenarios. As the discussion moves from the higher levels down to the engine room, each section maintains conceptual depth in an approachable format. The book isnโt tied to a specific technology like Kubernetes. Rather, it helps the reader understand the key decisions and trade-offs that a platform engineering team must make along the entire journey. Review: Must read for everybody involved in platform engineering - Centralising functionality into a platform is a pattern that has been used in IT for decades. But in many cases it has been done mainly for cost reasons with the result that the centralised platform became a huge bottleneck making fast innovation impossible. But doing platform right provides a lot of potential benefits for the enterprise: Reusablilty, alignment, better compliance and security posture, reduction of team cognitive load. Gregor Hohpe introduces a lot of patterns that can be applied when designing a platform, he discusses the benefits and disadvantages of different approaches and does all this in a very entertaining way. And not to forget, he introduces that pattern of "The Grim Wrapper". I thoroughly recommend this book to everybody involved in designing and implementing a shared platform. It definitely will make your product better. Review: Surpreendente - Minha mentalidade mudou depois desse livro
| Amazon ๅฃฒใ็ญใฉใณใญใณใฐ | ๆดๆธ - 6,053ไฝ ( ๆดๆธใฎๅฃฒใ็ญใฉใณใญใณใฐใ่ฆใ ) Computer Systems Analysis & Design - 9ไฝ Software Testing - 68ไฝ Software Development - 87ไฝ |
| ใใใใๅบฆ | 5ใคๆใฎใใก4.8 58 ใฌใใฅใผ |
R**A
Must read for everybody involved in platform engineering
Centralising functionality into a platform is a pattern that has been used in IT for decades. But in many cases it has been done mainly for cost reasons with the result that the centralised platform became a huge bottleneck making fast innovation impossible. But doing platform right provides a lot of potential benefits for the enterprise: Reusablilty, alignment, better compliance and security posture, reduction of team cognitive load. Gregor Hohpe introduces a lot of patterns that can be applied when designing a platform, he discusses the benefits and disadvantages of different approaches and does all this in a very entertaining way. And not to forget, he introduces that pattern of "The Grim Wrapper". I thoroughly recommend this book to everybody involved in designing and implementing a shared platform. It definitely will make your product better.
C**E
Surpreendente
Minha mentalidade mudou depois desse livro
V**L
Great book and would highly recommend. Full of practical insights.
Great book and would highly recommend. Full of practical insights. Thank you Gregor Hohpe and contributors.
R**R
Should be read by architecture teams everywhere.
Do you read a book to justify your strongly and long held beliefs? Or do you read a book to challenge your assumptions, possibly solidify some beliefs or get a perspective in an entirely new direction? Given that time is the one resource I have less and less of, Gregor never disappoints when I spend it reading his works.
J**N
Great book
A must read
Trustpilot
2 weeks ago
2 months ago