Each stage contains a
small, dynamically sized thread pool to drive its execution. SEDA provides
nonblocking I/O primitives to eliminate the most common sources of long
blocking operations.
In the ServiceMix SEDA flow, we have a simple event staging between the
internal processes in the NMR broker. SEDA is the default flow in ServiceMix
and is suited for general deployment, as the additional staging can buffer
exchanges between heavily routed to components (where state maybe used),
for example.
???
Chapter 3
[ 61 ]
The following figure represents a SEDA flow:
ServiceMix ESB
Staged
Delivery
Channel
Staged
Delivery
Channel
Binding
Service
Buffer
Buffer
NMR
Message
Flow
Java Message Service (JMS) flow: In the ServiceMix JMS flow, we can
leverage the tested and proven methodology of MOM to address scalability
or failover. Using JMS flow, multiple ServiceMix containers can collaborate in
a cluster or otherwise, to provide component and service replication. When
we deploy a component either as a POJO or as an archive component into a
JMS flow configured ServiceMix container, all the containers in the cluster
are notified of the deployment.
Pages:
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109