|
|
Featured White Papers
- Why choose an Open Source BPM?
- 10 FAQs on Business Process Management
- Best Practices for Getting Started with BPM
- Free Your Devs From The Pain Of Java Redeploys
- Increase Velocity 40% by Using JRebel
- What Developers Want: The End of Application Redeploys
- Developer Productivity Report: Java Tools, Tech, Devs, and Data
- Coding with JRebel: Java Forever Changed
- Utilizing Fast Testing to Transform Java Development
- Do You Really Get Classloaders?
- Pragmatic Continuous Delivery with Jenkins, Nexus, and LiveRebel
- Your Next Java Web App: Less XML, No Long Restarts, Fewer Hassles
- Coding with JRebel, Java Forever Changed
- 2012 Developer Productivity Report: Java Tools, Tech, Devs, and Data
Spring Integration application architecture
Submitted by stephanion2002 on Fri, 09/03/2010 - 14:00.
Tags:
Back to:
www.javaworld.com/javaworld/jw-12-2007/jw-12-springintegration.html.
Hi Paul,
Your post is informative, thanks !
I am aiming to create a notification server (a pub/sub and p2p model) and excited to use Spring Integration’s features. To make that notification server an isolated black box, I m thinking to expose its functionality thru rest based APIs. Since ActiveMQ is highly configurable so probably going to use it for the message management part.
Do You think that it’s a feasible & a wise decision to go for an architecture like this considering scalability & extensibilty ?
External systems > Restful APIs on Tomcat > Spring Integration acting as lightweight ESB > ActiveMQ (+MySql for message persistence and tomcat i.e. not the ‘embedded’ jetty) > Spring Integration > Restful APIs > External systems
What all pros & cons do you suggest in this scenario…..
Many thanks,
Kshitiz