My workspace

Apache Ignite is widely used around the world and is growing all the time. Companies like Barclays, Misys, Sberbank (3r largest bank in Europe), ING, JacTravel all use Ignite to power pieces of their architecture that are critical to the day-to-day operations of those organizations. Moreover, the vendor like TIBCO uses core caching data-grid module of Apache Ignite with advanced indexing and SQL capability for their Master Data Management platform. However there are a few others alternatives to Apache Ignite from other vendors such as HazelCast, Oracle, Ehcache, GemFire, etc. The main difference of Apache Ignite from the others is the number of functionalities and simplicity of use. Apache Ignite provides a variety of functionalities, which you can use for different use cases. The key differences between the Apache Ignite , Hazelcast , and Apache Cassandra are as follows: Feature Apache Ignite Hazelcast Apache Cassandra Data model Key-value ...

We are happy to introducing our new title " The Apache Ignite book ". The first portion of the book is being published a few days before by leanpub publication. Note that, the entire book is an agile published book, which means that the authors are releasing it as they write it and will continue to update the book as the underlying technology evolves over time. The sample chapter of the book is available in different formats including HTML . What you will learn: Apache Ignite architecture in depth such as data distributing technics (DHT), Rendezvous hashing, memory architecture, various topology and caching strategies. Apache Ignite use cases as a memory-centric distributed database, caching and computing platforms. Caching strategies and how to use Apache Ignite to improve the performance of the application. Using JPA with Apache Ignite for developing high-performance web applications . How to accelerates the performance of your existing Hadoop ecosystem withou...

UP1: if you are interested in in-memory computing, we recommended the book "High performance in-memory computing with Apache Ignite" . A few days ago we decided to use 2nd level cache for better java scalability in our legacy system. Everything goes fine with hazelcast as a 2nd level cache, whenever our a few 3rd party applications starts uploading data directly to the Oracle schema. Generally, a middle-tier data cache duplicates some data from the back-end database server. Its goal is to avoid redundant queries to the database. However, this is efficient only when the data rarely changes in the database. The data cache has to be updated or invalidated when the data changes in the database. If application operates DML operations through cache it's simply your life, but in our case some of our 3rd party can't use hazelcast data grid and we decided to get the proper way to update our caches or clear it whenever some entity on tables updates. In this post i will pr...