Apache Ignite Data Grid Research Corey Pentasuglia

What is Apache Ignite? In Memory Data Fabric An open source Apache Incubator project Started and still mostly maintained by a company named GridGain Ignite contains several key components for high performance computing within a distributed architecture

Data Grid Designed with scalability in mind Data locality is important and priority Data can be accessed via a HashMap of values, however the Grid also has support for standard SQL, including distributed SQL joins Implements the Jcache specification (as defined by Oracle)

Data Grid (Key Benefits) Allows for quick access to large amounts of data With the popularity of “Big Data” comes the necessity to quickly access that data Values are cached in memory When data is accessed on networked machines, the disk no longer needs to be accessed. The cache that’s stored in memory can be accessed much faster The cache is always kept in sync with the data within the DB The Ignite documentation suggests creating indexes to make queries even faster. In fact, Ignite even has an implementation for “In Memory Indexing”

Replicated Vs. Partitioned Cache Replicated Cache Creates a copy on every node of the cluster Slow updates Impacts performance and scalability High availability Partitioned Cache Distributed among nodes Faster updates Very scalable and high performance High availability as the number of nodes increases

Project (Two Parts) Utilize four of the Linux lab machines to test the distributed setup and caching A Java application is written and bundled to run on these machines which allows a distributed cache to be modified Perform a proof a concept on my own machine to test out the distributed cache and automatic persistence Run Ignite with a distributed cache that syncs with a MySQL DB running on my laptop

Project (Development Setup) Apache Ignite is fully “Mavenized”. Meaning all the dependency management and building can be configured in Apache Maven Installed on my laptop: Apache Maven 3.0.5 Netbeans IDE 8.1 Apache Ignite 1.4.0 MySQL Community Edition 5.7.9 Java applications created to run on the school machines will be bundled with dependencies to run independently using the Java –jar command (also known as a Super Jar)

Project (Lab Machines) The lab machines selected can be seen below Demonstration: While the plain Ignite installed can be started and utilized, I have created custom JAR files that contain my code These JARS can be run on any machine that has Java installed I will start my application on Spunky and add to the distributed cache I will then start my app on Goliath and query the cache This will demonstrate the caching portion of the DataGrid

Project (Laptop) This portion of the project was performed on my laptop Automatic Persistence Utilized the bundled Ignite tool to generate Java and XML code Write initialization code Created another Java project to interact with the DB through the cache (using generated code) Create an interface to perform SQL on the distributed DB Create an interface to perform lookups on the cache

Community

Citation https://ignite.apache.org/ (Entire website, documentation, images, and linked videos)