Welcome to the new Gigaspaces XAP forum. To recover your account, please follow these instructions.

Ask Your Question

Gigaspaces vs TIBCO Activespaces IMDG

Hi Team,

Could you help me to understand Gigaspaces with following questions?

  1. Do we have any performance metrics/comparison for Gigaspaces vs TIBCO Activespaces?

  2. Can I call Gigaspaces as pure Data Grid or it's still a cache? Reason : When a cache evicts an entry, it does it quietly and without telling any of it's clients about it. This means that you can not 'trust your data' to a cache as it could disappear from it at any time. What pattern is it using? Example : Cache Aside?

  3. How about Archieval & loading efficiency? If I use RDBMS like DB2/Sybase for persistance vs I use Apache Casandra/Mongo DB like IMDB for the same.

  4. Partitioning & High Availibility: In case, I want to increase memory, I can scale it linearly & it's quite flexible. But I am also not interested to evict entries from memory grid. New entry comes & I don't have space left, so in this case I am adding 1 more machine & starting my agent.

What will happen? Is there any downtime? As partitions are in place, will it try to redistribute entries in each partition to balance in each node?

Thanks Dharam

asked 2013-09-05 05:35:16 -0500

Dharam gravatar image
edit retag flag offensive close merge delete

1 Answer

Sort by ยป oldest newest most voted


Gigaspaces XAP is a universal app server with a universal data grid supporting in a native manner java , .Net and Cpp applications. It support all caching scenarios , fully transactional , cloud oriented. Gigaspaces XAP running in more than 20,000 systems world wide. GigaSpaces is totaly elastic , both on the data grid layer , its processing and compute nodes layers , totally scalable supporting millions of transactions per second. See example:


If you book a flight , perform a phone call , use your credit card , perform a financial trade , visiting an hospital and getting medications - you are probably being processed by a system based on GigaSpaces.

Millions of people rely on mission critical systems running GigaSpaces 24X7 for the last 10 years in a highly secured organizations with very minimal administration. Many billions of $ processed by GigaSpaces based systems every day.

GigaSpaces integrates with every database, relational or NOSQL including Cassandra and MongoDB or big data such as hadoop delivering real time transactional analytics fabric.

You may have all your data in memory as GigaSpaces support multiple Tera bytes in memory or have time/capacity based eviction or custom eviction.

You should consider GigaSpaces as the application system of record. That's how most of our customers are doing. It makes the overall architecture way simpler , scalable and reliable.

You can use both side cache or in-line cache architecture. It depends how you want the data grid will interact with the backend store. With side cache the app response the load/store data to the database. With in-line approach the data grid will load/store data to the database automatically.

Data will not be evicted unless you configure it to do that. You can increase the data grid capacity manually or dynamically without any downtime. I suggest you consider the above when comparing in-memory compute products.

If you need detailed benchmarks contact me: Shay at gigaspaces.com .


answered 2013-09-05 08:56:53 -0500

shay hassidim gravatar image

updated 2013-09-08 09:21:10 -0500

edit flag offensive delete link more

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Question Tools


Asked: 2013-09-05 05:35:16 -0500

Seen: 1,522 times

Last updated: Sep 08 '13