Strategic Monoliths and Microservices: Driving Innovation Using Purposeful Architecture (The Pearson Addison-Wesley Signature)

Strategic Monoliths and Microservices: Driving Innovation Using Purposeful Architecture (The Pearson Addison-Wesley Signature)

Taschenbuch
4.01

Durch das Verwenden dieser Links unterstützt du READO. Wir erhalten eine Vermittlungsprovision, ohne dass dir zusätzliche Kosten entstehen.

Beschreibung

Make Software Architecture Choices That Maximize Value and Innovation
"[Vernon and Jaskuła] provide insights, tools, proven best practices, and architecture styles both from the business and engineering viewpoint. . . . This book deserves to become a must-read for practicing software engineers, executives as well as senior managers."
--Michael Stal, Certified Senior Software Architect, Siemens Technology
Strategic Monoliths and Microservices helps business decision-makers and technical team members clearly understand their strategic problems through collaboration and identify optimal architectural approaches, whether the approach is distributed microservices, well-modularized monoliths, or coarser-grained services partway between the two.

Leading software architecture experts Vaughn Vernon and Tomasz Jaskuła show how to make balanced architectural decisions based on need and purpose, rather than 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 redesign and reimplement 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" Register your book for convenient access to downloads, updates, and/or corrections as they become available. See inside book for details.
Haupt-Genre
N/A
Sub-Genre
N/A
Format
Taschenbuch
Seitenzahl
348
Preis
37.44 €

Beiträge

1
Alle
4

This is a great book about the usual debate to either go for monolith or to use microservices like everyone else. It brings in some interesting points like FOMO in regards to tech and also summarises many other must-reads like [b: Team Topologies: Organizing Business and Technology Teams for Fast Flow|44135420|Team Topologies Organizing Business and Technology Teams for Fast Flow|Matthew Skelton|https://i.gr-assets.com/images/S/compressed.photo.goodreads.com/books/1563409554l/44135420._SX50_.jpg|68629236]. I especially like the mention of ADR and the examples - I think we really need documentation like this in our industry. One of the things I don't like is the kind-of difficult (at least for me) to understand insurance domain in the examples and also the many mentions of the upcoming book ([b: Implementing Strategic Monoliths and Microservices: Patterns and Practices for Continuous Improvement|61127814|Implementing Strategic Monoliths and Microservices Patterns and Practices for Continuous Improvement|Vaughn Vernon|https://i.gr-assets.com/images/S/compressed.photo.goodreads.com/books/1652960636l/61127814._SX50_.jpg|96350209]- it sometimes feels like you got only half of the text.

Beitrag erstellen