| 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... |
---|
| | | | | | |
Customer Reviews | | | | | | |
---|
Price | $53.35$53.35 | $58.70$58.70 | $44.94$44.94 | $53.35$53.35 | $31.74$31.74 | $52.17$52.17 |
---|
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. |
---|