Saved by Emi
What’s the Deal with Statebox, Anyway?
Exploring the problem space: a guide to building the right solution
culture.entelect.co.za
Each year, it took longer and longer to ship features to customers, and the risk of even small changes causing major problems kept growing. In 1998, developers could make changes and deploy them immediately. By 2004, pushing code changes into production required hours, even days, to be deployed.39 Teams were no longer able to solve Layer 1 problems
... See moreSteven J. Spear • Wiring the Winning Organization: Liberating Our Collective Greatness through Slowification, Simplification, and Amplification
Most commercial organizations face the following challenges when defining the architectures of their products: Focus on technology details rather than business context. Perception of architects as not delivering solutions or adding value. Inability of architectural practices to address the increase in speed of IT delivery and to adapt to modern del
... See morePierre Pureur • Continuous Architecture in Practice: Software Architecture in the Age of Agility and DevOps (Addison-Wesley Signature Series (Vernon))
This basic stack is so accepted (and frankly so much easier now with AWS etc.) that we rarely question it. But it's ridiculously inefficient. Why should every potential business need to build all 3 parts of this stack when their core innovation or value add comes primarily from one or two?