Dani Traphagen is a solution architect for GridGain, where she consults on high-tech caching architectures. Previously, Dani consulted at DataStax and led technical training internationally on Apache Cassandra and DataStax Enterprise. Her passion for teaching began while working in the Electrical Engineering and Computer Science department at the University of California, Berkeley, where she taught scientists technical skills, helped create a data science course, and raised awareness about the growing open science community. Dani has since volunteered with and generated training content for a number of organizations, including software carpentry, women in technology, rOpenSci, and GitHub. Earlier in her career, Dani worked in cartilage tissue engineering at the University of California, San Francisco, where her interests for heavy machinery, science, and code fused. If you don’t catch Dani behind a computer, you’ll often see her in the wild, backpacking, riding her bike, or climbing things. She also makes sure to keep the coffee business afloat in her hometown of Hermosa Beach.
In this post, I will cover the changes in Apache® Ignite™ 2.0/2.1 (which tracks to GridGain 8.0/8.1) that are important when implementing a project in Ignite. Then we will discuss the easiest way to setup a cache and just use the basic functionality of the Data Grid.
So, Apache Ignite 2.0 & 2.1 have dropped! This is awesome news for you as a user. This is fun times for us at GridGain…