G
Gervas
You are probably familiar with JMS and other traditional
message-oriented middleware, not to mention other loose and tightly
coupled flavours of middleware. Want something less brittle and
automatically adaptable to changing application structures (ever come
across a staic app structure??)? Have a look at an article in the
Inquirer offering a free software download. You can find it at:
http://www.theinquirer.net/?article=15197
The middleware in question, AutevoSpaces, is an implementation of
Sun's JavaSpaces with the following enhancements:
• Single System Image Clustering. This allows a single virtual
AutevoSpace to be distributed across multiple servers with obvious
scalability and failover benefits, whilst requiring no code change to
the application.
• Evolution allows different simultaneous views of the same Java
object from different clients. Multiple versions of the same service,
or multiple services can make updates to the same instance of an
object without any loss of data. This facilitates non-disruptive,
system transition with non-stop operation, as well as concurrent
operation of different application/data model versions. It also allows
disparate systems to interact with a common information model in a
truly collaborative, bi-directional manner, updating the model as they
need to, and seeing what they need to. In the real world this means
that existing systems can remain in place while they themselves are
able to participate in the incremental evolution of the information
model.
Gervas
message-oriented middleware, not to mention other loose and tightly
coupled flavours of middleware. Want something less brittle and
automatically adaptable to changing application structures (ever come
across a staic app structure??)? Have a look at an article in the
Inquirer offering a free software download. You can find it at:
http://www.theinquirer.net/?article=15197
The middleware in question, AutevoSpaces, is an implementation of
Sun's JavaSpaces with the following enhancements:
• Single System Image Clustering. This allows a single virtual
AutevoSpace to be distributed across multiple servers with obvious
scalability and failover benefits, whilst requiring no code change to
the application.
• Evolution allows different simultaneous views of the same Java
object from different clients. Multiple versions of the same service,
or multiple services can make updates to the same instance of an
object without any loss of data. This facilitates non-disruptive,
system transition with non-stop operation, as well as concurrent
operation of different application/data model versions. It also allows
disparate systems to interact with a common information model in a
truly collaborative, bi-directional manner, updating the model as they
need to, and seeing what they need to. In the real world this means
that existing systems can remain in place while they themselves are
able to participate in the incremental evolution of the information
model.
Gervas