{"product_id":"continuous-architecture-in-practice-9780136523567","title":"Continuous Architecture in Practice","description":"\u003cb\u003eBook Synopsis\u003c\/b\u003e\u003cbr\u003e\u003cdiv\u003e  \u003cb\u003eMurat Erder\u003c\/b\u003e has more than twenty-five years' experience in the software industry working for software vendors, management consultancies and large international banks. During his career Murat has had a variety of roles, from developer, to software architect, to management consultant. Murat's corporate IT roles cover the areas of data, integration, architecture and working as a CTO. He is co-author of the book  \u003ci\u003eContinuous Architecture: Sustainable Architecture in an Agile and Cloud-Centric World\u003c\/i\u003e (2015) and has presented on this topic at a range of conferences, including SEI Saturn, O'Reilly Software Architecture and GOTOLondon.   \u003cbr\u003e \u003c\/div\u003e \u003cdiv\u003e  \u003cbr\u003e \u003c\/div\u003e \u003cdiv\u003e  \u003cb\u003ePierre Pureur\u003c\/b\u003e is an experienced software architect, with extensive innovation and application development background, vast exposure to the financial services industry, broad consulting experience and comprehensive technology infrastructure knowledge. His past roles include serving as Chief En\u003cbr\u003e\u003cbr\u003e\u003cb\u003eTrade Review\u003c\/b\u003e\u003cbr\u003e\" \u003ci\u003eContinuous Architecture in Practice\u003c\/i\u003e captures the key concerns of software architects today, including security, scalability and resilience, and provides valuable insights into managing emerging technologies such as machine\/deep learning and blockchain. A recommended read!\" \u003cbr\u003e \u003ci\u003e--Jan Bosch, Professor of Software Engineering and Director of the Software Center at Chalmers University of Technology, Sweden\u003c\/i\u003e \u003cbr\u003e \u003cbr\u003e\" \u003ci\u003eContinuous Architecture in Practice\u003c\/i\u003e is a great introduction to modern-day software architecture, explaining the importance of shifting architectural thinking 'left' in order to form a set of firm foundations for delivery and continuous architecture evolution. I really liked the coverage of quality attributes, with a real-world case study providing a way to highlight the real-world complexities of the trade-offs associated with different solutions. The set of references to other material is impressive too, making this book incredibly useful for readers new to the domain of software architecture.\" \u003cbr\u003e \u003ci\u003e--Simon Brown, author of \u003c\/i\u003eSoftware Architecture for Developers \u003cbr\u003e \u003cbr\u003e\"In our ever-changing world of increasing system complexity, the responsibilities and skills required to be a software architect must continually evolve. Successfully adapting to constant requirements, technology, and business changes requires an architect to be multi-skilled, capable in engineering and technology, business and management. The role of architect has never been more challenging. \u003cbr\u003e \u003cbr\u003e\"This is why \u003ci\u003eContinuous Architecture in Practice\u003c\/i\u003e is an important book for all architects to absorb. The principles-based approach espoused in this book can be used to guide architects in charting a successful path in a broad range of project contexts. The essential activities for software architects present an excellent overview of the core professional skills an agile architect must possess, regardless of the problem domain and technologies in use. \u003cbr\u003e \u003cbr\u003e\"Most notably, the book devotes chapters to the key run-time quality attributes that drive modern systems. Security, performance, scalability, and resilience are the lifeblood of Internet-facing systems. Each chapter provides a contemporary overview of the characteristics of these quality attributes and explains tactics an architect can adopt to design and evolve systems that are built for long term survival. An additional chapter on data architectures recognizes an important system component that is rarely covered in architecture books. Data lies at the heart of most systems and creating resilient and scalable data architectures exploiting modern data technologies is a skill all architects should have. \u003cbr\u003e \u003cbr\u003e\"Written in an approachable, concise, and informative style, with concepts illustrated using an ongoing case study, this is an excellent book that will help architects address the many challenges of engineering systems in the 2020s and beyond. It is a deep source of knowledge suitable for practicing and aspiring architects, and an advanced college course in software architecture. It will repay the time investment many times over.\" \u003cbr\u003e \u003ci\u003e--Professor Ian Gorton, Northeastern University\u003c\/i\u003e \u003cbr\u003e \u003cbr\u003e\"Focus on software architecture can get lost when talking about agile software practices. However, the importance of architecture in software systems has always been and continues to be relevant. The authors address this important topic with their second book on Continuous Architecture. This time they provide advice on aspects that will make or break your system, from data to security, scalability and resilience. A much recommended book that offers practical guidance for anyone developing systems in today's rapidly evolving technology landscape.\" \u003cbr\u003e \u003ci\u003e--Ivar Jacobson\u003c\/i\u003e \u003cbr\u003e \u003cbr\u003e\"This book continues the journey where its predecessor left off. Software today is never-ending, and true to its name, this book looks at continuing trends and applies Continuous Architecture principles using practical examples. The authors avoid the trap of picking popular tools whose relevance quickly expire, choosing instead to look at those trends that should influence and shape architecture decisions. This book will be essential reading for any person wanting to design and architect software systems that continue to keep up with the times.\" \u003cbr\u003e \u003ci\u003e--Patrick Kua, CTO Coach and Mentor\u003c\/i\u003e \u003cbr\u003e \u003cbr\u003e\"In the two-decade-old conflict between 'big upfront design' and 'emergent architecture,' software architects have often had a hard time finding a meaningful compromise. In \u003ci\u003eContinuous Architecture in Practice\u003c\/i\u003e, Erder, Pureur, and Woods provide them with a proven path. This book is a big leap forward: I liked the more systematic use of architectural tactics--a design artifact that has not been exploited as much as it should. And that they brought the concept of architectural technical debt to a more prominent position in the process of making technical and managerial decisions.\" \u003cbr\u003e \u003ci\u003e--Philippe Kruchten, software architect\u003c\/i\u003e \u003cbr\u003e \u003cbr\u003e\"It's high time that Agile architecture evolved from oxymoron to what it really needs to be, a lean, enabling practice that accelerates development and delivery of the next generation of resilient and scalable enterprise class systems. \u003ci\u003eContinuous Architecture in Practice\u003c\/i\u003e is another quantum step toward that goal and provides practical guidance toward creating designs that are responsive to changing requirements and technologies.\" \u003cbr\u003e \u003ci\u003e--Dean Leffingwell, creator of SAFe\u003c\/i\u003e\u003cbr\u003e\u003cbr\u003e\u003cb\u003eTable of Contents\u003c\/b\u003e\u003cbr\u003e\u003ci\u003eForeword by Vaughn Vernon, Series Editor xv\u003cbr\u003eForeword by Kurt Bittner xix\u003cbr\u003eIntroduction xxi\u003cbr\u003eAcknowledgments xxv\u003cbr\u003eAbout the Authors xxvii\u003c\/i\u003e \u003cbr\u003e \u003cbr\u003e \u003cb\u003eChapter 1: Why Software Architecture Is More Important than Ever 1\u003c\/b\u003e \u003cbr\u003eWhat Do We Mean by Architecture? 1 \u003cbr\u003eSoftware Industry Today 3 \u003cbr\u003eCurrent Challenges with Software Architecture 5 \u003cbr\u003eSoftware Architecture in an (Increasingly) Agile World 8 \u003cbr\u003eIntroducing Continuous Architecture 11 \u003cbr\u003eApplying Continuous Architecture 17 \u003cbr\u003eIntroduction to the Case Study 19 \u003cbr\u003eSummary 22 \u003cbr\u003e \u003cbr\u003e \u003cb\u003eChapter 2: Architecture in Practice: Essential Activities 23\u003c\/b\u003e \u003cbr\u003eEssential Activities Overview 24 \u003cbr\u003eArchitectural Decisions 26 \u003cbr\u003eQuality Attributes 32 \u003cbr\u003eTechnical Debt 36 \u003cbr\u003eFeedback Loops: Evolving an Architecture 42 \u003cbr\u003eCommon Themes in Today's Software Architecture Practice 48 \u003cbr\u003eSummary 54 \u003cbr\u003e \u003cbr\u003e \u003cb\u003eChapter 3: Data Architecture 55\u003c\/b\u003e \u003cbr\u003eData as an Architectural Concern 56 \u003cbr\u003eKey Technology Trends 60 \u003cbr\u003eAdditional Architectural Considerations 76 \u003cbr\u003eSummary 84 \u003cbr\u003eFurther Reading 85 \u003cbr\u003e \u003cbr\u003e \u003cb\u003eChapter 4: Security as an Architectural Concern 87\u003c\/b\u003e \u003cbr\u003eSecurity in an Architectural Context 88 \u003cbr\u003eArchitecting for Security 92 \u003cbr\u003eArchitectural Tactics for Mitigation 101 \u003cbr\u003eMaintaining Security 115 \u003cbr\u003eSummary 119 \u003cbr\u003eFurther Reading 119 \u003cbr\u003e \u003cbr\u003e \u003cb\u003eChapter 5: Scalability as an Architectural Concern 123\u003c\/b\u003e \u003cbr\u003eScalability in the Architectural Context 124 \u003cbr\u003eArchitecting for Scalability: Architecture Tactics 134 \u003cbr\u003eSummary 155 \u003cbr\u003eFurther Reading 156 \u003cbr\u003e \u003cbr\u003e \u003cb\u003eChapter 6: Performance as an Architectural Concern 159\u003c\/b\u003e \u003cbr\u003ePerformance in the Architectural Context 159 \u003cbr\u003eArchitecting for Performance 163 \u003cbr\u003eSummary 183 \u003cbr\u003eFurther Reading 184 \u003cbr\u003e \u003cbr\u003e \u003cb\u003eChapter 7: Resilience as an Architectural Concern 187\u003c\/b\u003e \u003cbr\u003eResilience in an Architectural Context 188 \u003cbr\u003eArchitecting for Resilience 195 \u003cbr\u003eArchitectural Tactics for Resilience 200 \u003cbr\u003eMaintaining Resilience 216 \u003cbr\u003eSummary 222 \u003cbr\u003eFurther Reading 223 \u003cbr\u003e \u003cbr\u003e \u003cb\u003eChapter 8: Software Architecture and Emerging Technologies 225\u003c\/b\u003e \u003cbr\u003eUsing Architecture to Deal with Technical Risk Introduced by New Technologies 226 \u003cbr\u003eIntroduction to Artificial Intelligence, Machine Learning, and Deep Learning 227 \u003cbr\u003eUsing Machine Learning for TFX 230 \u003cbr\u003eUsing a Shared Ledger for TFX 246 \u003cbr\u003eSummary 257 \u003cbr\u003eFurther Reading 258 \u003cbr\u003e \u003cbr\u003e \u003cb\u003eChapter 9: Conclusion 259\u003c\/b\u003e \u003cbr\u003eWhat Changed and What Remained the Same? 259 \u003cbr\u003eUpdating Architecture Practice 261 \u003cbr\u003eData 263 \u003cbr\u003eKey Quality Attributes 264 \u003cbr\u003eThe Architect in the Modern Era 267 \u003cbr\u003ePutting Continuous Architecture in Practice 268 \u003cbr\u003e \u003cbr\u003e \u003cb\u003eAppendix A: Case Study 269\u003cbr\u003e\u003cbr\u003eAppendix B: Comparison of Technical Implementations of Shared Ledgers 299\u003c\/b\u003e \u003cbr\u003e \u003cbr\u003e \u003ci\u003eGlossary 301\u003cbr\u003eIndex 311\u003c\/i\u003e\n\u003c\/div\u003e","brand":"Pearson Education (US)","offers":[{"title":"Default Title","offer_id":48864173818199,"sku":"9780136523567","price":29.69,"currency_code":"GBP","in_stock":true}],"thumbnail_url":"\/\/cdn.shopify.com\/s\/files\/1\/0817\/1739\/5799\/files\/9780136523567.jpg?v=1722270737","url":"https:\/\/bookcurl.com\/products\/continuous-architecture-in-practice-9780136523567","provider":"Book Curl","version":"1.0","type":"link"}