Books

Today's applications rarely live in isolation. Users expect instant access to all functions, which may be provided by disparate applications and services, inside or outside the enterprise. Integrating applications and services remains more difficult than it should be, though: developers have to deal with asynchrony, partial failures, and incompatible data models. The lack of a common vocabulary and body of knowledge for asynchronous messaging architectures made it difficult to avoid common pitfalls.

That's why Bobby Woolf and I documented a pattern language consisting of 65 integration patterns to establish a technology-independent vocabulary and a visual notation to design and document integration solutions. Each pattern not only presents a proven solution to a recurring problem, but also documents common "gotchas" and design considerations.

The patterns are brought to life with examples implemented in messaging technologies, such as JMS, SOAP, MSMQ, .NET, and other EAI Tools. The solutions are relevant for a wide range of integration tools and platforms, such as IBM WebSphere MQ, TIBCO, Vitria, WebMethods (Software AG), or Microsoft BizTalk, messaging systems, such as JMS, WCF, Rabbit MQ, or MSMQ, ESB's such as Apache Camel, Mule, WSO2, Oracle Service Bus, Open ESB, SonicMQ, Fiorano or Fuse ServiceMix.

label Intigration-patterns, Integration, Enterprise

0 Comments

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

label architecture

0 Comments