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
Report an issue with this product or seller
Customers who viewed this item also viewed
From the brand
-
Software Development
-
Software Architecture
-
Software Engineering
-
More From O'Reilly
-
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.
Head First Software Architecture: A Learner's Guide to Architectural Thinking
|
Fundamentals of Software Architecture: A Modern Engineering Approach
|
Communication Patterns: A Guide for Developers and Architects
|
The Software Architect Elevator: Redefining the Architect's Role in the Digit...
|
Software Architecture: The Hard Parts: Modern Trade-Off Analyses for Distribu...
|
Facilitating Software Architecture: Empowering Teams to Make Architectural De...
|
|
|---|---|---|---|---|---|---|
| What is it? | Head First Software Architecture teaches you how to think architecturally and explores the unique challenges of software architecture, using a visually rich format to engage your mind. | A comprehensive overview of aspects of software architecture including architectural characteristics, architectural patterns, diagramming and presenting architecture, evolutionary architecture, and more. | A comprehensive guide to communicating software architecture. Learn how to successfully present your architecture and get stakeholders to jump on board. | Learn how to combine organizational and technical knowledge in order to effect change in your company’s structure and processes. | There are many hard parts in software architecture that force you to choose among various compromises. This book teaches you how to think critically about the trade-offs. | Explore how teams can collaborate on the architectures of their systems to ensure that everyone and everything is working toward the same goal. |
| What you'll learn | The distinction between architecture and design; the relationship between code, components, and architectural styles; and how to work with common architectural styles. | How to use architecture patterns and make architectural decisions; how to use coupling, cohesion, partitioining, and granuality; soft skills; and engineering practices. | How to design appropriate diagrams and documentation, and master written, verbal, and nonverbal communication to succeed in technical settings. | How to work with an organization as a whole, connecting the IT engine room to the penthouse, where the business strategy is defined. | How to determine service granularity, manage workflows and orchestration, manage and decouple contracts, and manage distributed transactions to how to optimize operational characteristics. | How to create a collaborative, decentralized mindset that allows everyone to do architecture and build the best systems they've ever experienced. |
| Who is this book for? | If you're a software developer looking for a quick on-ramp to software architecture, this handy guide is a great place to start. | Senior software developers, aspiring and 'accidental' software architects, and software architects looking to solidify their knowledge. | Software developers and software architects who want to learn how to communicate their architectures effectively. | Software architects, senior developers, enterprise architects and senior technologists. | Software architects who are ready to delve into the 'hard parts' of software architecture. | Those who are in a position to affect change in how their software is architected and designed and are inclined to try something new. |
| Who else is it for? | Those who want to gain an understanding of architectural dimensions and understand the differences between architecture and design. | Those in other roles that need to understand the main concepts of software architecture. | Those in other roles that work with software architecture and want to understand diagrams and documentation further. | CTOs, senior technical architects and IT managers who are devising an IT strategy that impacts the way the organization works. | Those in other roles who would like to understand more about the complex decisions in software architecture. | Traditional decision-makers (aka architects) who know that ‘doing architecture the way we always have’ no longer works, as well as developers keen to step up and take on architecture responsibility. |
Product Videos
