Download or read book Strategic Monoliths and Microservices written by Tomasz Jaskula and published by . This book was released on 2021 with total page 368 pages. Available in PDF, EPUB and Kindle. Book excerpt: Make Architecture Choices That Free You to Maximize Value and Innovation "The heart of this book is a large set of thinking tools that will help you design a new architecture . . . and the organization needed to support that architecture. The book then offers ways to gradually move from your existing architecture toward the new one. . . . There is no formula for success other than the one offered [here]: highly skilled people, deep thinking, and constant experimentation." --From the Foreword by Mary Poppendieck, coauthor, Lean Software Development Strategic Microservices and Monoliths helps business decision-makers and technical team members collaborate to clearly understand their strategic problems and identify their optimal architectural approaches, whether these prove to be distributed microservices, well-modularized monoliths, or coarser-grade services partway between the two. Leading software architecture experts Vaughn Vernon and Tomasz Jaskua show how to make balanced architecture decisions based on need and purpose, not hype so you can promote value and innovation, deliver more evolvable systems, and avoid costly mistakes. Using realistic examples, they show how to construct well-designed monoliths that are maintainable and extensible, and how to gradually tease out even the most tangled legacy systems into truly effective microservices. Link software architecture planning to business innovation and digital transformation Overcome communication problems to promote experimentation and discovery-based innovation Master practices that support your value-generating goals and help you invest more strategically Compare architectural styles that can lead to versatile, adaptable applications and services Recognize when monoliths are your best option and how best to architect, design, and implement them Learn when to move monoliths to microservices and how to do it, whether they're modularized or a "Big Ball of Mud"