This document introduces Apache Ignite, an open source in-memory computing platform that provides in-memory caching, data grid, and database capabilities. It is supported by GridGain Systems and graduated from Apache in 2015. Key features include ACID compliance, SQL support, and the ability to perform both online transaction processing and online analytical processing. The document discusses Apache Ignite architecture, partitioning vs replication, consistency models, and use cases for in-memory caching, data grids, and databases. It also compares Ignite to other in-memory solutions and outlines approaches for data persistence and high availability.

1. Apache Ignite介紹及使用案例

2. Apache Ignite
 Supported by GridGain Systems
 2015, graduated from Apache.
 ACID, SQL
 OLTP + OLAP = HATP
 In-Memory Cache
 In-Memory Data Grid
 In-Memory Database
Java-based
In-Memory Computing Platform (Hybrid Transaction/Analytical Processing)

3. Feature Compares
In-Memory Data Grid (IMDG)

4. Apache Ignite and GridGain Overview

5. Data Grid – Client & Server node
TcpDiscoverySpi & ZookeeperDiscoverySpi

6. Apache Ignite Architecture
可嵌入到Application Server，亦可使用外部的Cluster
1 Embedded with the application Client & server in the same host2 Multi-node within single JVM3

7. Partitioned vs Replicated

8. Apache Ignite & CAP theorem
Atomic mode = AP
Transaction mode = CP
Hot/Cold date = Cache Life Cycle

9. In-Memory Cache

10. Web Session
1. Session 3 無法跨出
Server 3的範圍
2. Server重起，Session
3資料將消失
3. Cookie是用戶端
Session是伺服器端
一般Session是限定在單一Application Server的Memory之中

11. Use Case - Web Session Clustering
可嵌入到Application Server，亦可使用外部的Cluster

12. In-Memory Database

13. In-Memory + Third Party Database
Ignite Web Console + Ignite Web Agent

14. In-Memory DB Persistence Architecture
持久儲存方式：
1. 儲存在WAL檔案。
2. WAL檔案逐漸增大，避
免叢集重建需從頭讀到尾，
使用checkpointing方式。
Write-Ahead Log & Checkpointing

15. IMDG vs IMDB
Different with In-Memory Data Grid and In-Memory DataBase

16. 相關書籍
https://github.com/srecon/the-apache-ignite-book/