> Expanding that out a bit, a co-worker and I have been experimenting
> with Gigaspaces (which includes Jini, Rio, etc. And Intel Capital has
> in investment in GS.)
>
> What we are doing now is starting with HTTP, URIs, and Atom and then
> looking at where to use the GS capabilities both on the implementation
> side (integration with legacy systems, etc.) as well as on the
> "client" side.
>
> A "client" can use the system via HTTP-based resources directly,
> eventually we'll look at XMPP as well, or through Jini
> capabilities. That could include SOAP as a "legacy" capability,
> although many of my co-workers would cringe at my labeling SOAP as
> "legacy".
Gigaspaces has shown how you can apply different strategies of access to a
distributed memory/data model. They have a very powerful and capable system for
a wide range of enterprise data needs. If you don't need all the interworkings
with outside systems and you are using Java, you can start with a simpler
Javaspaces implementation such as the Outrigger service that comes with the
JTSK, or you can use Dan Creswells Blitz service which has some extra features.
When you get to the point of needing something else, you can inject something
like GigaSpaces, and because you are using standard APIs, and because of the
dynamics of Jini, you can turn GS on, and your other javaspace off (if you which
to switch), and your clients will switch over (if you've done your homework on
configuration and service lifecycle management).
With point to point client service architectures, things might have to get more
touchy feely.
Gregg Wonderly
SPONSORED LINKS
| Computer software | Computer aided design software | Computer job |
| Soa | Service-oriented architecture |
YAHOO! GROUPS LINKS
- Visit your group "service-orientated-architecture" on the web.
- To unsubscribe from this group, send an email to:
[EMAIL PROTECTED]
- Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.
