Skip to main content

The full table of contents of the book High Performance in-memory computing with Apache Ignite

The book High Performance in-memory computing with Apache Ignite has been completed and available at LeanPub.


Table of contents:

  • Introduction
    • What is Apache Ignite
    • Who uses Apache Ignite
    • Why Ignite instead of others
    • Our Hope
  • Chapter one: Installation and the first Ignite application
    • Pre-requirities
    • Installation
    • Run multiple instances of Ignite in a single host
    • Configure a multi-node cluster in different host
    • Rest client to manipulate with Ignite
    • Java client
    • SQL client
    • Conclusion
    • What's Next
  • Chapter two: Architecture overview
    • Functional overview
    • ClusterTopology
      • Client and Server
      • Embedded with the application
      • Server in separate JVM (real cluster topology)
      • Client and Server in separate JVM on single host
    • Caching Topology
      • Partitioned caching topology
      • Replicated caching topology
      • Local mode
    • Caching strategy
      • Cache-aside
      • Read-through and Write-through
      • Write behind
    • Data model
    • CAP theorem and where does Ignite stand in?
    • Clustering
      • Cluster group
      • Data collocation
      • Compute collocation with Data
      • ZeroSPOF
    • How SQL queries works in Ignite
    • Multi-data center replication
    • Asynchronous support
    • Resilience
    • Security
    • KeyAPI
    • Conclusion
    • What's next
  • Chapter three: In-memory caching
    • Apache Ignite as a 2nd level cache
      • MyBatis 2nd level cache
      • Hibernate 2nd level cache
    • Java method caching
    • Web session clustering with Apache Ignite
    • Apache Ignite as a big memory, off-heap memory
    • Conclusion
    • What’s next
  • Chapter four: Persistence
    • Persistence Ignite’s cache
      • Persistence in RDBMS (PostgreSQL)
      • Persistence in MongoDB
    • Cache queries
      • Scan queries
      • Text queries
    • SQL queries
      • Projection and indexing with annotations
      • Query API
      • Collocated distributed Joins
      • Non-collocated distributed joins
      • Performance tuning SQL queries
    • Apache Ignite with JPA
    • Expiration & Eviction of cache entries in Ignite
      • Expiration
      • Eviction
    • Transaction
      • Ignite transactions
      • Transaction commit protocols
      • Optimistic Transactions
      • Pessimistic Transactions
      • Performance impact on transaction
    • Conclusion
    • What’s next
  • Chapter five: Accelerating BigData computing
    • Hadoop accelerator
      • In-memory Map/Reduce
      • Using Apache Pig for data analysis
      • Near real-time data analysis with Hive
      • Replace HDFS by Ignite In-memory File System (IGFS)
      • Hadoop file system cache
    • Ignite for Apache Spark
      • Apache Spark – an introduction
      • IgniteContext
      • IgniteRDD
    • Conclusion
    • What’s next
  • Chapter six: Streaming and complex event processing
    • Introducing data streamer
      • StreamReceiver
      • StreamVisitor
    • IgniteDataStreamer
      • Direct Ingestion
      • Mediated Ingestion
    • Camel data streamer
    • Flume streamer
    • Storm data streamer
    • Conclusion
    • What’s next
  • Chapter seven: Distributed computing
    • Compute grid
      • Distributed Closures
      • MapReduce and Fork-join
      • Per-Node share state
      • Distributed task session
      • Fault tolerance & checkpointing
      • Collocation of compute and data
      • Job scheduling
    • Service Grid
      • Developing services
      • Cluster singleton
      • Service management & configuration
    • Developing microservices in Ignite
Labels:

Comments

Post a Comment

Popular posts from this blog

8 things every developer should know about the Apache Ignite caching

Any technology, no matter how advanced it is, will not be able to solve your problems if you implement it improperly. Caching, precisely when it comes to the use of a distributed caching, can only accelerate your application with the proper use and configurations of it. From this point of view, Apache Ignite is no different, and there are a few steps to consider before using it in the production environment. In this article, we describe various technics that can help you to plan and adequately use of Apache Ignite as cutting-edge caching technology. Do proper capacity planning before using Ignite cluster. Do paperwork for understanding the size of the cache, number of CPUs or how many JVMs will be required. Let’s assume that you are using Hibernate as an ORM in 10 application servers and wish to use Ignite as an L2 cache. Calculate the total memory usages and the number of Ignite nodes you have to need for maintaining your SLA. An incorrect number of the Ignite nodes can become a b...
Post a Comment
Read more

Tip: SQL client for Apache Ignite cache

A new SQL client configuration described in  The Apache Ignite book . If it got you interested, check out the rest of the book for more helpful information. Apache Ignite provides SQL queries execution on the caches, SQL syntax is an ANSI-99 compliant. Therefore, you can execute SQL queries against any caches from any SQL client which supports JDBC thin client. This section is for those, who feels comfortable with SQL rather than execute a bunch of code to retrieve data from the cache. Apache Ignite out of the box shipped with JDBC driver that allows you to connect to Ignite caches and retrieve distributed data from the cache using standard SQL queries. Rest of the section of this chapter will describe how to connect SQL IDE (Integrated Development Environment) to Ignite cache and executes some SQL queries to play with the data. SQL IDE or SQL editor can simplify the development process and allow you to get productive much quicker. Most database vendors have their own fron...
Post a Comment
Read more

Load balancing and fail over with scheduler

Every programmer at least develop one Scheduler or Job in their life time of programming. Nowadays writing or developing scheduler to get you job done is very simple, but when you are thinking about high availability or load balancing your scheduler or job it getting some tricky. Even more when you have a few instance of your scheduler but only one can be run at a time also need some tricks to done. A long time ago i used some data base table lock to achieved such a functionality as leader election. Around 2010 when Zookeeper comes into play, i always preferred to use Zookeeper to bring high availability and scalability. For using Zookeeper you have to need Zookeeper cluster with minimum 3 nodes and maintain the cluster. Our new customer denied to use such a open source product in their environment and i was definitely need to find something alternative. Definitely Quartz was the next choose. Quartz makes developing scheduler easy and simple. Quartz clustering feature brings the HA and...
Post a Comment
Read more