Spring Integration application architecture

[stephanion2002]

Hi all,

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

[Mascotte]

Hello,

seems quite complicated. The double use of Spring-integration and Active MQ schould be considered carefully. What are you trying to do with ActiveMQ, you can't do with Spring Integration ?
I have not all context elements, but I would suggest either to build a full Spring-based solution or a full JMS-based solution.

What about your real messaging needs ? your performance constraints ?

Regards,
Matthias Feraga.

[stephanion2002]

Thanks for the reply Mascotte !

For demo perspective, I have dropped the idea to have spring integration and just using activemq ..thanks for suggesting not to have them both.

[stephanion2002]

Changed the architecture again

I am currently working on this model: Publisher->Restlet->Spring Integration->SpringAMQP->RabbitMQ->Consumers

[Mascotte]

Once again I don't know what you are assuming to do,
but it seems to be a good tradeoff and at least a widely used messaging pattern