1

I am planning to use Spring Integration as my lightweight messaging solution avoiding JMS or MQ. My requirement is when an event A happens there should process B and C triggered asynchronously with some inputs supplied by A. It will not be a single JVM so I am planning to use JDBC message-store.

  • Is SI best tool to solve this?
  • How difficult is it to maintain our message store that backs pollers (need to write our own polling SQL query?) .
  • Will it create table contentions while deleting message from the persistent table?
  • How to ensure that the thread pool is effectively utilized?
iwein
  • 25,788
  • 10
  • 70
  • 111
Kay Gee
  • 259
  • 1
  • 5
  • 15
  • 1
    I don't understand "It will not be a single JVM so i'm planning to use JDBC message-store" how are those two related exactly? – iwein Oct 23 '12 at 20:29

1 Answers1

0

If you are just using JDBC for distribution rather than persistence, you'd be better off distributing the event to the other JVMs using a lightweight adapter such as UDP or TCP.

Gary Russell
  • 166,535
  • 14
  • 146
  • 179