posted 13 years ago
Btw, when you think of Spring Integration, think of lightweight integration frameworks. An ESB by its very definition mandates a central server through which everything flows. Spring Integration is not a server, it has no startup scripts, no requirements on infrastructure, etc. If you want to provide integration support in your web application but don't want to deploy a whole new broker, that's easy. If you want to deploy an application that handes integration between two systems, then you can do that, too. Spring Integration makes no prescription about where it's run or how. It's just an API with libraries that implement support for connecting to, and sending and receiving events from, external systems. I like to think of Spring Integration as the first member of the fledgling NoESB movement ;-)
Thanks, Josh Long
Spring Developer Advocate, SpringSource, a division of VMware
http://blog.springsource.org - http://www.joshlong.com