Making Big Data work...

Red Hat release JBoss Data Grid 6 Beta

Chris Mayer

The beta for Red Hat’s highly scalable, distributed, in-memory database that lets you scale cost-effectively has arrived.

Scaling on your mind? Well it should be if you’re thinking about
making the next step for your business web application as it
garners more critical acclaim and popularity.

But of course, that old stumbling block of bottlenecks is
stopping you from making the commitment. Have no fear, Red Hat have
released the latest version of their in-memory database
finely-tuned for easing the transition to a Big Data approach,
without compromises.

Capable of working with applications written in Java, Spring or
C#, Red Hat JBoss Data Grid 6 can be deployed in
an application server or on its own. The NoSQL data store claims to
be incredibly flexible in what data it stores and to be a reliable
alternative for replicating data across a large number of

The distribution options are plentiful; you can replicate data
in-memory, write to disk, or store it in a relational database for

Crucially for applications wanting little disruption, Data Grid
6 beta allows simple addition or removal of storage nodes without
any impact on performance. Another sticking point for any
enterprise wondering whether to make the jump over to a NoSQL
approach is how this data is accessed. Fortunately Data Grid 6 has
a plethora of choices here – each providing easy access
to the data grid using REST, memcached, Hot Rod, or simple map-like

Already helping data-intensive applications within sectors like
online retail and financial trading boost performance and
scalability, Red Hat JBoss Data Grid 6 continues upon the good work
by bringing in some new features and could well become the popular
choice of NoSQL in-memory data stores. Intrinsically linked to
Infinispan and JBoss EAP 6, Data Grid 6 could indeed become part of
the JBoss developer’s inventory for solving some of the problems
within the Big Data minefield.

You can download the beta
, so get tinkering.

comments powered by Disqus