Spring Integration实战指南：英文版PDF

5星 · 超过95%的资源需积分: 9 123 浏览量更新于2024-07-21 2 收藏 15.01MB PDF 举报

《Spring Integration in Action》是一本由Mark Fisher、Jonas Partner、Marius Bogoevici和Iwein Fuld合著的专业IT技术书籍，英文版PDF格式。该书是Spring Integration领域的重要参考资料，Spring Integration 是一个广泛应用于企业级应用集成的框架，它允许开发者构建可扩展且易于管理的消息驱动系统。Spring Integration基于Spring框架，集成了多种消息传递技术，如JMS、AMQP、HTTP、FTP等，使得在复杂的应用环境中实现异步处理和数据交换变得更加容易。书中内容深入浅出，不仅介绍了Spring Integration的基本概念、架构和工作原理，还涵盖了如何设计和实现集成解决方案的具体步骤。作者们从理论到实践，提供了大量实例和最佳实践，帮助读者理解如何将Spring Integration与现有的Spring应用程序无缝集成，以及如何利用其强大的功能来提升系统的可靠性和性能。本书前言由Rod Johnson撰写，他是Spring框架的创始人之一，他的引言可能包含对Spring Integration框架的历史背景、核心价值以及其在现代软件开发中的重要性的阐述。资源提供方Manning Publications Co.强调了版权保护，并给出了购买和获取更多关于该书和其他曼宁出版社书籍的信息方式，包括在线购买链接、折扣政策和联系方式。同时，对于制造商和销售商的产品名称，书中会尊重商标权益，使用全大写或首字母大写的格式标注。阅读这本书对于任何希望深入了解Spring Integration并将其应用于实际项目中的IT专业人士来说都极具价值，无论是初学者还是经验丰富的开发人员，都能从中收获实用的知识和技能，提高企业的系统集成能力。

foreword

Integration is currently a hot topic. We live in an increasingly asynchronous world in

which we need to interact with a bewildering range of systems, so our software applica-

tions need to support a variety of conversation patterns with disparate collaborators.

Software that helps developers tackle this complexity is crucial. In the 2000s,

Struts, Spring, and Hibernate replaced in-house web MVC, configuration, and persis-

tence code with superior, battle-tested, and well-documented open source code. Simi-

larly today, integration is core to so many applications that we need quality, generic

infrastructure in place of ad hoc solutions.

Spring Integration is a great choice to address these infrastructure requirements.

Too many open source projects reinvent every wheel in sight. Spring Integration does

not, and is stronger for it. It explicitly builds on established best practices and existing

software. Spring Integration was inspired by one of the classic books on enterprise

software: Hohpe and Woolf’s Enterprise Integration Patterns (Addison-Wesley, 2003). The

developers chose to follow the vocabulary that book introduced, meaning that their

code benefits from the thinking and experience that’s evident in the book and is easy

for developers familiar with those patterns to adopt. Spring Integration also builds on

the powerful and proven Spring Framework. It extends Spring’s POJO programming

model, making it a natural choice for the millions of developers already familiar with

Spring. If you’re a Spring developer, learning Spring Integration won’t feel so much

like learning a new framework as like picking up a part of the Spring Framework core

that you haven’t yet applied. You’ll be able to focus on mastering architectural con-

cepts without wrestling with an unfamiliar API. Spring Integration also applies proven

FOREWORDxvi

Spring values such as portability, with the result that it can be used in a wide range of

environments.

Spring Integration is set to become an increasingly important project within the

Spring Portfolio. I believe this book will become the definitive work on it.

The authors are uniquely qualified to write about the topic. Mark Fisher is the cre-

ator and lead of Spring Integration, and all the authors are contributors. Their daily

involvement in the open source project has ensured that the book is up to date with

Spring Integration 2.0 features and best practices. Mark, Marius, Iwein, and Jonas

have a wealth of worldwide consulting experience helping customers solve integration

problems. This extensive and current hands-on experience underpins their writing

and offers great value to the reader.

The authors do an excellent job of putting Spring Integration in context. Rather

than merely explain how to use Spring Integration, they discuss common business

problems, the trade-offs between potential solutions, and how Spring Integration can

be applied to implement them. The first few chapters explain how Spring Integration

grows naturally out of the Spring Framework.

The examples are well chosen: easy to grasp, yet realistic enough to communicate

real-world problems. A good balance between code examples and explanation devel-

ops the reader’s understanding at a steady pace.

There are many highlights, but I particularly like chapter 18, “Testing.” In this, as

in many other chapters, you’ll find a wealth of good advice based on experience,

which will save you a lot of time debugging. What kinds of tests will give you the most

bang for your buck? How do you test your configuration? How do you figure out

what’s going on with an endpoint that has no output? You’ll find thoughtful answers

to these and many other questions.

Finally, Spring Integration in Action is well written. Too often technical books are

clumsily and sloppily worded, making them hard work to plow through and poten-

tially confusing. This book is an exception, being enjoyable to read and always clear

and to the point. Excellent, uncluttered diagrams elucidate many key points.

I hope you enjoy reading Spring Integration in Action. I did.

OD JOHNSON

FOUNDER OF THE SPRING FRAMEWORK

xvii

preface

As I write this in August 2012, I find it difficult to believe that nearly five years have

passed since we officially launched the Spring Integration project. I guess, as they say,

time flies when you’re having fun, and I would add that it flies even faster (especially

the weekends) when you’re writing a book. For those who have been anxiously await-

ing a print copy since this book project was first announced in Manning’s Early Access

Program, I hope you find it worth the wait.

One thing is certain: the authors are true subject matter experts. Each of my coau-

thors has contributed to the framework, and many of the chapters are written by the

one person most intimately familiar with the topic at hand. In a few cases, new fea-

tures were even added to the framework based on ideas that originated in the book.

The degree of expertise is most apparent, however, in the frequent discussions about

design decisions and the trade-offs involved. In those sections, I believe the reader will

fully recognize that the authors’ perspectives have been shaped by real-world experi-

ence building enterprise integration solutions.

The first prototype that eventually led to the official launching of the Spring Inte-

gration project was a result of two motivations. First, I had been deeply inspired by the

indispensable Enterprise Integration Patterns written by Gregor Hohpe and Bobby Woolf

(Addison-Wesley, 2003). Second, I quite literally had a life-changing experience with

the Spring Framework. I was determined to bring those two forces together in a way

that would let them both shine.

Regarding the

EIP book, I probably have one of the most well-worn copies, and it’s

always within easy reach at my desk. To this day I refer to it regularly, even for some-

thing as mundane as settling upon the right terminology to use in code documenta-

tion. By the time I first read that book, I had experience with several integration

frameworks and containers, and yet I felt that none truly captured the essence of

PREFACExviii

those patterns. I wanted to define an API that would be immediately accessible to any-

one familiar with the patterns, where not only the functionality but the vocabulary

could be easily recognized.

As for my life-changing experience with the Spring Framework, in late 2005, a for-

tunate series of events led to my joining the core team. The company behind Spring,

Interface21, had recently been established, and as an employee I quickly went from

being just a Spring fanatic to being a full-time consultant, trainer, and contributor.

In those early days, I spent a majority of my time on the road. I worked on site with

dozens of organizations, trained hundreds of engineers, and spoke at numerous user

groups and conferences. Throughout those interactions, I noticed that developers

became genuinely excited about the Spring Framework once they experienced the

proverbial “aha!” moment. Soon, my primary goal was to elicit a similar reaction from

users of a new extension to the Spring programming model that would focus on the

enterprise integration patterns. That pretty much sums up why I started the project.

Much of the groundwork for Spring Integration was coded on the go—in planes,

trains, taxis, hotel lobbies, and countless cafes. Throughout my travels, I demon-

strated the early prototypes, and I processed vast amounts of feedback. My colleagues

at Interface21 provided their share of honest feedback, including Rod Johnson,

founder of the Spring Framework, who took an early interest in the project.

Interface21 later evolved into SpringSource which was in turn acquired by

VMware. Today, I continue to lead the integration efforts within the Spring team at

VMware. Now it’s much more common for me to write code at a desk, and in fact the

majority of new Spring Integration code is currently written by others on the team.

I’ve also been pleased to see the number of community contributors grow, a trend

that should lead to many extensions to the core.

Ironically, as the founder of the project, I have a particularly difficult time devising

its “elevator pitch.” I suppose it’s always a challenge to avoid verbosity when discussing

something that you live and breathe day after day. That said, based on the background

I provided here, such a pitch might go something like this:

Spring Integration provides support for the enterprise integration patterns while

building upon the Spring programming model. It shares the Spring Framework’s goal

of simplifying the developer role as much as possible. This goal is applicable even, and

perhaps especially, when the developer is designing and implementing applications

that aren’t simple at all. It’s a fact of life that modern applications are increasingly

complex since they tend to require event-driven services interacting with data in near-

real time across a wide variety of distributed systems. Those are the problems that the

enterprise integration patterns address, and applying the Spring programming model

to those patterns exposes their full power through a simplified developer experience.

Indeed, Spring Integration enables developers to implement those distributed, event-

driven applications. It does so in a way that keeps the enterprise integration patterns

in clear focus and maintains the associated vocabulary as accurately as possible. Above

all, I hope you find that it does so in a way that lets the developer enjoy the journey and

that this book gets you started on the right path.

MARK FISHER

剩余366页未读，继续阅读

sinat_19461273

粉丝: 0
资源: 2

Spring Integration实战指南：英文版PDF

Spring-Integration-in-Action：本书随附的源代码

spring_integration_in_action.pdf

Spring Integration API（Spring Integration 开发文档）.CHM

Spring Batch in Action英文pdf版

Spring_in_Action.pdf

Spring In Action 英文原版第二版

Manning.Spring.Batch.in.Action.Oct.2011

springDM开发指南（英文）

Spring实战(第二版)英文高清PDF

Spring实战第三版：探索Spring 3.0

最新资源