Skip to main content

Implementing @ApacheIgnite's cache store (part II)

Apache Ignite’s CacheStore interface is an API for cache persistence storage for read-through and write-through behavior.  When implementing this interface, you choose the type of key and value object alike -- similar to a map.  This follows the pattern established by the CacheLoader and CacheWriter interfaces CacheStore extends of the JSR107 specification.  In many cases, having a specific implementation for each method when implementing this interface may not be necessary, so Apache Ignite has a CacheStoreAdapter for this purpose.

Since Caches so closely resemble Maps, perhaps we should begin our discussion with a cache implementation that is essentially a HashMap store:

public class HashMapStore extends CloudStoreAdapter {

private final Map<Object, Object> map = new HashMap<>();

@Override public void loadCache(IgniteBiInClosure c, Object … args) {

for(Map.Entry e : map.entrySet()) {
c.apply(e.getKey(), e.getValues());

@Override public Object load(Object key) {
Return map.get(key);

@Override public void write(Cache.Entry e) {
map.put(e.getKey(), e.getValue());

@Override public void delete(Object key) {

To use an Ignite cache, a configuration must be provided.  This can be done several ways -- including declaratively using a Spring XML configuration or programmatically using Ignite’s native CacheConfiguration object.

    Ignite’s CacheConfiguration class extends the MutableConfiguration class of the JSR107 specification.  When configuring an Ignite cache, out of the dozens of settings to choose from there are some settings that are at least as important as setting the name of the cache.  One of these settings is the write synchronization mode.  Each mode setting indicates how ignite should wait for write replies from other nodes.  The three possible settings as provided by the CacheWriteSynchronizationMode enum are FULL_SYNC, FULL_ASYNC, and PRIMARY_SYNC.  The standard setting is FULL_SYNC.  This setting guarantees that whenever any of the atomic or transactional writes complete, all other participating nodes which cache the written data has been updated.



Popular posts from this blog

More Guice Please!!!: Re-Learning Google's Agile Lightweight Dependency Injection Library (Part 1.1)

Google Guice is used as a lightweight dependency injection framework that further assists developers in modularizing their applications.  Google shared this very useful library with the development community in 2010 in between the Java SE 6 and Java SE 7 releases.  This library is used in some of Java’s (and now Scala’s) most prominent libraries and platforms such as the Simian Army platform shared by Netflix.
We will begin our discussion of Google Guice with its Module interface.  In the Guice developers’ own words, ‘A Guice-based application is ultimately composed of little more than a set of modules and some bootstrapping code.’  We will not be using this interface directly, but it gives us a very good context from which to start.  Instead, we will be extending the abstract class that implements it -- intuitively named AbstractModule.  
If you ever get a chance to look at the Module interface JavaDoc or source code, you’ll see a configure method taking a parameter of type Binder.  

#processing @Microsoft #office #Excel files with @TheASF POI (part II)

     Apache POI's OPCPackage abstract class represents a container that can store multiple data objects.  It is central to the processing of Excel(*.xlsx) files.  We only need to use its static open method to process an InputStream instance.  Further, we can "read" these Excel files via the XSSFWorkbook class.  This class is a high level representation of a SpreadsheetML workbook.  From an XSSFWorkbook, we can get any existing XSSFSheets within the workbook.  Then, we can further subdivide any XSSFSheet into rows and analyze the cell data within the rows.  In general, given certain assumptions in the format of the Excel document, we can extract data as text  from a cell and perform any number of business processes.

     In the Java function code excerpt below, we assume we have an Excel(*.xlsx) file represented as an InputStream.

    public Iterator<Row> apply(InputStream inputStream) {

        try(OPCPackage pkg =…