A practical, nuts-and-bolts guide to architectural solutions that describes step-by-step how to design robustness and flexibility into an Internet-based system Based on real-world problems and systems, and illustrated with a running case study Enables software architects and project managers to ensure that nonfunctional requirements are met so that the system won't fall over, that it can be maintained and upgraded without being switched off, and that it can deal with security, scalability, and performance demands Platform and vendor independence will empower architects to challenge product-dictated limitations

The popularity of enterprise architecture (EA) has increased in the last two decades, in both business and academic domains. Despite the cumulative interest from all sectors, the implementation and practice of EA have been entangled with numerous challenges and complexities. Consequently, some organisations continue to theorise the concept, which has ramifications on practice and return on investment (ROI). This has led to many studies that have been conducted, to understand the complexities impacting the implementation and practice of EA in organisations. Yet, the trajectory of some convolutions remains mystery in many quarters. This attributes to the struggle to articulate the value of EA in many environments. Hence many organisations find it difficult to apply EA for strategic management of modern information technology (IT) solutions. Enterprise Architecture for Strategic Management of Modern IT Solutions provides guidance on how to employ EA in deploying and managing IT solutions from pragmatic and implementable strategies’ perspectives. Until now, implementation and practice of EA have been slow, despite its growing popularity and interest from all sectors. The author employs sociotechnical theories such as actor-network theory (ANT) and structuration theory (ST) as lenses to examine and explain why and how challenges and complexities exist and derail the implementation or practice of EA in organisations. By doing so, this serves to enable practitioners and readers to gain fresh insights on why the challenges exist and how they can be addressed in creating collaborative capabilities for business enhancement, sustainability, and competitiveness. The book provides detailed insights on how to apply EA for organisational purposes, from three main fronts. First, it explains the implications that lack of understanding of EA have on organisational activities and processes. Second, it examines the challenges and complexities that hinder the implementation and practice of EA in organisations. Third, it proposes models and frameworks on how EA can be applied for strategic management of modern IT solutions in organisations. Written for postgraduates, researchers, academics, and professionals in the fields of EA, IT, and information systems, this book provides a valuable resource that will enable and enhance implementation and practice of EA including future studies.

Every enterprise architect faces similar problems when designing and governing the enterprise architecture of a medium to large enterprise. Design patterns are a well-established concept in software engineering, used to define universally applicable solution schemes. By applying this approach to enterprise architectures, recurring problems in the design and implementation of enterprise architectures can be solved over all layers, from the business layer to the application and data layer down to the technology layer. Inversini and Perroud describe patterns at the level of enterprise architecture, which they refer to as Enterprise Architecture Patterns. These patterns are motivated by recurring problems originating from both the business and the underlying application, or from data and technology architectures of an enterprise such as identity and access management or integration needs. The Enterprise Architecture Patterns help in planning the technological and organizational landscape of an enterprise and its information technology, and are easily embedded into frameworks such as TOGAF, Zachman or FEA. This book is aimed at enterprise architects, software architects, project leaders, business consultants and everyone concerned with questions of IT and enterprise architecture and provides them with a comprehensive catalogue of ready-to-use patterns as well as an extensive theoretical framework to define their own new patterns.

Demystify architecting complex blockchain applications in enterprise environments Architecting Enterprise Blockchain Solutions helps engineers and IT administrators understand how to architect complex blockchain applications in enterprise environments. The book takes a deep dive into the intricacies of supporting and securing blockchain technology, creating and implementing decentralized applications, and incorporating blockchain into an existing enterprise IT infrastructure. Blockchain is a technology that is experiencing massive growth in many facets of business and the enterprise. Most books around blockchain primarily deal with how blockchains are related to cryptocurrency or focus on pure blockchain development. This book teaches what blockchain technology is and offers insights into its current and future uses in high performance networks and complex ecosystems. Provides a practical, hands-on approach Demonstrates the power and flexibility of enterprise blockchains such as Hyperledger and R3 Corda Explores how blockchain can be used to solve complex IT support and infrastructure problems Offers numerous hands-on examples and diagrams Get ready to learn how to harness the power and flexibility of enterprise blockchains!

The practice of enterprise application development has benefited from the emergence of many new enabling technologies. Multi-tiered object-oriented platforms, such as Java and .NET, have become commonplace. These new tools and technologies are capable of building powerful applications, but they are not easily implemented. Common failures in enterprise applications often occur because their developers do not understand the architectural lessons that experienced object developers have learned. Patterns of Enterprise Application Architecture is written in direct response to the stiff challenges that face enterprise application developers. The author, noted object-oriented designer Martin Fowler, noticed that despite changes in technology--from Smalltalk to CORBA to Java to .NET--the same basic design ideas can be adapted and applied to solve common problems. With the help of an expert group of contributors, Martin distills over forty recurring solutions into patterns. The result is an indispensable handbook of solutions that are applicable to any enterprise application platform. This book is actually two books in one. The first section is a short tutorial on developing enterprise applications, which you can read from start to finish to understand the scope of the book's lessons. The next section, the bulk of the book, is a detailed reference to the patterns themselves. Each pattern provides usage and implementation information, as well as detailed code examples in Java or C#. The entire book is also richly illustrated with UML diagrams to further explain the concepts. Armed with this book, you will have the knowledge necessary to make important architectural decisions about building an enterprise application and the proven patterns for use when building them. The topics covered include · Dividing an enterprise application into layers · The major approaches to organizing business logic · An in-depth treatment of mapping between objects and relational databases · Using Model-View-Controller to organize a Web presentation · Handling concurrency for data that spans multiple transactions · Designing distributed object interfaces

A software architect’s digest of core practices, pragmatically applied Designing effective architecture is your best strategy for managing project complexity–and improving your results. But the principles and practices of software architecting–what the authors call the “science of hard decisions”–have been evolving for cloud, mobile, and other shifts. Now fully revised and updated, this book shares the knowledge and real-world perspectives that enable you to design for success–and deliver more successful solutions. In this fully updated Second Edition, you will: Learn how only a deep understanding of domain can lead to appropriate architecture Examine domain-driven design in both theory and implementation Shift your approach to code first, model later–including multilayer architecture Capture the benefits of prioritizing software maintainability See how readability, testability, and extensibility lead to code quality Take a user experience (UX) first approach, rather than designing for data Review patterns for organizing business logic Use event sourcing and CQRS together to model complex business domains more effectively Delve inside the persistence layer, including patterns and implementation.

As the digital economy changes the rules of the game for enterprises, the role of software and IT architects is also transforming. Rather than focus on technical decisions alone, architects and senior technologists need to combine organizational and technical knowledge to effect change in their company’s structure and processes. To accomplish that, they need to connect the IT engine room to the penthouse, where the business strategy is defined. In this guide, author Gregor Hohpe shares real-world advice and hard-learned lessons from actual IT transformations. His anecdotes help architects, senior developers, and other IT professionals prepare for a more complex but rewarding role in the enterprise. This book is ideal for: Software architects and senior developers looking to shape the company’s technology direction or assist in an organizational transformation Enterprise architects and senior technologists searching for practical advice on how to navigate technical and organizational topics CTOs and senior technical architects who are devising an IT strategy that impacts the way the organization works IT managers who want to learn what’s worked and what hasn’t in large-scale transformation