SURINDER29 T H JULY, 2016
In-Memory Data Fabric
Apache Ignite 1.5
Data Fabric
Introduction
A collection of independent, well-integrated, in-memory components
high-performance, integrated and distributed in-memory platform
transacting on large-scale data sets in real-time
faster than possible with traditional disk-based or flash technologies
Data Grid
Distributed In-Memory Caching
Implements JCache (JSR 107)
Distributed In-Memory Transactions
Data ConsistencyTiered Off-Heap
StorageDistributed ANSI-99
SQL Queries with support for Joins
Keep required backup Everyone knows everything
Cache Modes
Cache Queries…
Scan Query : return data matching BiPredicate Predicate sent to each node, Node scan its cache Data consolidated by requested node
Sql Query : load data based on sql given Needs indexing to be enabled Registering indexing in config Annotations for fields visibility H2 Console for debugging
Text Query : Query cache object on given value TextQuery txt = new TextQuery(Person.class, "Master Degree");
Cache Queries contd..
Continuous Query : listens to change in data that fall into filter Initial Query(any of fro previous slide) Remote Filter : evaluate the key on primary node to
notify local listener about the changes Local Listener : Perform the intended task when it get
notification about the change in data.
Off Heap Memory
data can be stored and moved between on-heap, off-heap, and swap space
On Heap Tiered : stores on heap, evict to off heap and then may evict to swap space(default mode)
Off Heap Tiered : bypass on heap, may evict to swap space
Off Heap Values : Keys On heap and values off Heap. Useful when keys are small and values are huge
Swap Space : Disk space to evict data exceeding on heap and off heap
Eviction Policies
LRU : recommended when in doubtFIFO : it ignores the element access orderRandom
Randomly evict any element Used for debugging
Not beneficial when data fits in memory
Persistent Store
CacheStore implements cacheLoader and cacheWriter from JCache
Read throughWrite throughWrite behindWorks behind the cache API’s
Data Rebalancing
Used when new node join the gridPossibly more backups than configured in such
scenariosRebalance Modes
SYNC: cache calls blocked until rebalancing is completed ASYNC: rebalancing happen in background. Cache respond
immediately NONE : No rebalancing, cache loaded on demand when
required or explicitly loading
Questions
Top Related