I read this book as an Associate SE and I gained a ton of knowledge. This book is extremely well written. I enjoyed the order in which the topics were presented. It began with an explanation of the four pillars in software architecture. By doing so readers gain immediate value within the first few pages. I particularly enjoyed the advocation for a domain partitioned folder structure as opposed to a technically partitioned folder structure, especially for front end developers. I believe navigating the code base should very much resemble navigating the UI. This is not only cool for readability, but it inherently increases cohesion. A huge win for such a low cost.
After getting the foundations laid the authors explain different architecture styles. The part I found to be most useful was the charts they provided which give star ratings to highlight the strength and weaknesses of each architecture. This illustrates that architecture styles should be chosen for specific solutions and not trends. I gained the skills necessary to begin to think like an architect. It included breadth of knowledge which, as the book will tell you, is much more important than depth of knowledge for an architect. Then the authors decided to dive back in and elaborate a bit more on the foundations learned at the beginning. It suggested ADRs, another quick win for low costs. They also spoke about risks storming and offered friendly advice on finding balance within the teams.
All in all, an amazing book. And at the end, the authors even presented tons of short answer questions to challenge readers and really take the lesson home.
Enjoy fast, free delivery, exclusive deals, and award-winning movies & TV shows with Prime
Try Prime
and start saving today with fast, free delivery
Loading your book clubs
There was a problem loading your book clubs. Please try again.
Not in a club? Learn more
Join or create book clubs
Choose books together
Track your books
Bring your club to Amazon Book Clubs, start a new book club and invite your friends to join, or find a club that’s right for you for free.
Download the free Kindle app and start reading Kindle books instantly on your smartphone, tablet, or computer - no Kindle device required.
Read instantly on your browser with Kindle for Web.
Using your mobile phone camera - scan the code below and download the Kindle app.
Follow the authors
Something went wrong. Please try your request again later.
Frequently bought together
$43.99
Get it as soon as Saturday, Apr 6
In Stock
Total price:
To see our price, add these items to your cart.
Choose items to buy together.
More items to explore
Page 1 of 1 Start overPage 1 of 1
Popular Highlights in this book
Everything in software architecture is a trade-off. First Law of Software ArchitectureHighlighted by 928 Kindle readers- All architectures become iterative because of unknown unknowns, Agile just recognizes this and does it sooner.Highlighted by 764 Kindle readers
- Why is more important than how. Second Law of Software ArchitectureHighlighted by 369 Kindle readers
From the brand
-
-
Sharing the knowledge of experts
O'Reilly's mission is to change the world by sharing the knowledge of innovators. For over 40 years, we've inspired companies and individuals to do new things (and do them better) by providing the skills and understanding that are necessary for success.
Our customers are hungry to build the innovations that propel the world forward. And we help them do just that.
From the Publisher
From the Preface
Mathematicians create theories based on axioms, assumptions for things indisputably true. Software architects build axioms as well, but the software world is, well, softer than mathematics: fundamental things continue to change at a rapid pace in the software world.
The software development ecosystem exists in a constant state of dynamic equilibrium: while it exists in a balanced state at any given point in time, it exhibits dynamic behavior over the long term. A great modern example of the nature of this ecosystem follows the ascension of containerization and the attendant changes wrought: tools like Kubernetes didn’t exist a decade ago, yet now entire software conferences exist to service its users. The software ecosystem changes fractally: one small change causes another small change; when repeated hundreds of time, it generates a new ecosystem.
Architects have an important responsibility to continue to question assumptions and axioms left over from previous eras. Many of the books about software architecture were written in an era that only barely resembles the current world.
In fact, the authors believe that we must question fundamental axioms on a regular basis, in light of improved engineering practices, operational ecosystems, software development processes—everything that makes up the messy, dynamic equilibrium where architects and developers work each day.
|
|
|
|
|---|---|---|---|
| Software Architecture: The Hard Parts | Building Evolutionary Architectures | The Software Architect Elevator | |
| Customer Reviews | 474
| 334
| 335
|
| Price | $38.98 | $67.54 | $45.79 |
| Related Titles | Modern Tradeoff Analysis for Distributed Architectures | Support Constant Change | Redefining the Architect's Role in the Digital Enterprise |
Videos
Page 1 of 1Start OverPage 1 of 1
Videos for this product
0:07
Click to play video
Customer Review: Some pictures print are not clear at all
Noor
Reviews with images
Thorough overview of basics
The book is what it says: fundamentals... "just enough" of software architecture. Full of good advice for someone who already has some tech lead and design experience, but looking to move up in the hierarchy. General direction is more on breadth (architects) rather than on depth (developers). See picture for recommended study environment.
Top reviews from the United States
There was a problem filtering reviews right now. Please try again later.
Reviewed in the United States on November 7, 2021
Reviewed in the United States on December 15, 2023
Reviewed in the United States on October 1, 2020
Reviewed in the United States on June 18, 2022
Reviewed in the United States on September 17, 2022
The book is what it says: fundamentals... "just enough" of software architecture. Full of good advice for someone who already has some tech lead and design experience, but looking to move up in the hierarchy. General direction is more on breadth (architects) rather than on depth (developers). See picture for recommended study environment.
Images in this review
Reviewed in the United States on January 4, 2023
