Gigaspaces launches eXtreme Application Platform

Print Friendly, PDF & Email

GigaSpaces logoGigaspaces today is announcing release of version 6.0 of their eXtreme Application Platform.

From the release

As part of the new product release, GigaSpaces has embraced a much simpler, non-intrusive programming model that allows developers to write their applications in Plain Old Java Objects (POJOs), plain .Net and plain C++ objects. For Java, GigaSpaces is achieving this by supporting the Spring Framework, which is rapidly becoming the de-facto standard in Enterprise Java programming. GigaSpaces will continue supporting the other standard APIs in the product, including JavaSpaces, JMS, JDBC and Jcache

You’ll recall that Gigaspaces provides infrastructure software for enterprises that enables developers to write their business logic as if writing to a single computer and then scale out the application on multiple processors running on multiple machines. Gigaspaces solutions provide a platform for implementing high performance and scalable service-oriented architectures.

One thing I am not clear on is the difference between Gigaspaces’ offering and Digipede’s. John from Digipede has graciously educated me on the Digipede framework. If someone from those companies (or a customer) would care to outline some of the differences, I’m sure everyone would appreciate it.


  1. Let’s see if I can’t get this started. The Application pattern will make the call of value for these frameworks. Gigaspaces, based on the open source Javaspaces reference implementation, has what one might call a balanced software architecture.

    Compute throughput is captured in the notion above of ‘writing to a single computer and then scale out the application on multiple processors.’ The “balance” enters when the application grid is combined with the data grid. In many scenarios in HPC, getting data to the application is the bottleneck. Data Grid addresses the I/O component within it context. Orchestrating an application grid and a data grid allows jobs and data to be intelligently located.

    The new bindings appear to extend this to other languages allowing non-grid application access to the capability. Some might achieve a similar end via DRMAA. However, that still leaves the data i/o issues open.

    Of course the value of this depends on your problem.

  2. John — We would be happy to schedule a briefing with you to talk about GigaSpaces. Please send me an email if you would like to do so.

    Geva Perry