Intuition about SwarmESB: http://salboaie.github.com/
- abstraction build over asynchronous messages…. yes you can repeat this but it is not very useful.
- you put your APIs (functions, calls to web services, basic building blocks of logic,etc) in nodes and you compose all these in a special language that get executed by jumping from node to node. Makes sense to you?
Why is called swarming?
- because I like organic metaphors
- because jumping from node to node (using the network) of a set of values can be seen as sending messages but can be seen also as a swarming of some mysterious bees that care the honey (values ) . After a swarm reaches a node, it can swarm again and again and you can describe and understand in a single place all the related swarming activities started in a node . What can be cooler than that?
It is not somehow similar to SOA?
Yes it is. It is trying to solve similar concerns and actually it can work well in a SOA environment.
SwarmESB is really an ESB?
ESB have many meanings but basically, by swarming we are targeting the orchestration and loose coupling issues that all ESB are trying to address.