Sporty little number, Hazelcast Striim Hot Cache 13

Open source in-memory data grid (IMDG) company Hazelcast has worked with Striim (sounds like ‘stream’, get it?), a provider of end-to-end real-time data integration and streaming analytics to announce Hazelcast Striim Hot Cache.

This integration is supposed to enable real-time, push-based propagation of changes from the database to the cache.

Where this works is for for organisations that manage high volumes of data, the Hot Cache product ensures continuous synchronisation between the cache and its underlying database, providing consistency with the system of record.

One-to-one relationship

Traditionally, if there is a one-to-one relationship between an application and its underlying database (and no other applications or systems are able to make changes to that database) then the intermediary cache stays in-sync with the database.

However, if changes are made to the database directly by other applications, then data held in the cache immediately becomes stale. A common workaround to this problem is 1Ctime to live 1D or TTL. This is when companies purge documents from the database after a period of time.  For many this is a 1Cnear enough 1D solution. However, the process lowers cache efficiency and is inadequate for businesses that manage high transaction data or need to maintain high levels of customer experience. 

According to the firms, “The full data for the change is available to Striim. An Object Relational configuration is provided for each cache, so that the changes can be applied to the domain model in Hazelcast. These changes can be inserts, updates and deletes. During transformation, Striim can also perform data enrichment (joining CDC updates with other data, or performing aggregation and more complex processing) before writing the Object to the cache.”

Striim offers a CDC Wizard to speed deployment. Users can quickly configure the capture of change data from a variety of databases (including Oracle, MS SQL Server, MySQL and HPE NonStop), and propagate that data to their Hazelcast cache.  No configuration is required in Hazelcast.