Patterns in cluster

[vromero]

Some of the EIA patters might have problems in clusters when not using a shared state.

i.e :

[FONT=Courier New]

Splitter ---Producer1--> JMS/AMQP --Consumer1--> Aggregator
--Consumer2--> Aggregator
--Consumer3--> Aggregator

Does SI support some kind of clustering shared state for this kind of patterns?

[Mark Fisher]

In the example you've posted, the Aggregator is the stateful component, and our Aggregator's are using a MessageStore strategy for which we provide several options. Obviously the default (which simply uses an in-memory Map) is not useful in a clustered environment or in any situation where you want to persist in-progress messages (i.e. so you don't lose them in a crash). We do provide several implementations that are backed by a common data store: JDBC, GemFire, MongoDB, and Redis.

[vromero]

Hi Mark,

Thats awesome,

Just found it in the documentation also (I didn't before), sorry for asking here.