Cloud Native Transformation: Practical Patterns for Innovation
1: Architect products; evolve from projects to products. Architecting products is more efficient than just designing point solutions to projects and focuses the team on its customers. Principle 2: Focus on quality attributes, not on functional requirements. Quality attribute requirements drive the architecture. Principle 3: Delay design decisions u
... See morePierre Pureur • Continuous Architecture in Practice: Software Architecture in the Age of Agility and DevOps (Addison-Wesley Signature Series (Vernon))
In the vast majority of cases, a start big, all-in, bet-the-farm approach is an antipattern. It is not applying an agile mindset to agility. It fails to acknowledge that organizations are complex adaptive systems, that both change itself and changing how you perform that change are emergent, that humans have a limited velocity to unlearn and relear
... See moreJonathan Smart • Sooner Safer Happier: Antipatterns and Patterns for Business Agility
Even so, problems will occur when trying to apply Bounded Contexts with distributed computing before the teams have a good reason to, or when trying to understand the strategic goals and solve business problems using single-process modularity first. Such a bias will likely lead to over-engineered technical approaches, putting too much emphasis on t
... See moreTomasz Jaskula • Strategic Monoliths and Microservices: Driving Innovation Using Purposeful Architecture (Addison-Wesley Signature Series (Vernon))
Use the following principles for getting started:14 Ensure you have a clearly defined direction The direction should succinctly express the business or describe organizational outcomes you wish to achieve in measurable terms, even if they look like an unachievable ideal. Most importantly, it should inspire everyone in the organization. Think of HP
... See more