Skip to main content

Apache Ignite quick start guide

Recently we made a massive update on our lean publishing book The Apache Ignite Book. The book still is in progress. However, for the developers who intended to a quick start with Apache Ignite, we restructured the Sample chapter such a way that can be used as a quick start guide. We included the entire chapter 2 Getting started with Apache Ignite and most of the part of chapter 4 Architecture deep dive.


We believe the best way to learn something new is to jump right in and do a simple example to play around it. Whenever you had a decent overview of what you could do with this technology, you could always find more details later. The document is well structured and guides you from installing and running Ignite to write an advanced application to read and write data from/to the Apache Ignite database. The Apache Ignite quick start guide covers the following topics:

Chapter: Getting started with Apache Ignite
  • Installing and setting up Apache Ignite.
  • Running multiple instances of Apache Ignite in a single host.
  • Running Apache Ignite from Docker.
  • Using Apache Ignite SQLLINE command line tool for querying tables. • Meet with Apache Ignite SQL engine: H2 database.
  • Apache Ignite thin client.
  • Using a universal SQL client IDE to working with Apache Ignite.
  • First Java application.
  • Using REST application to manipulate with the Apache Ignite.
  • Configure a multimode cluster in different hosts.
  • A simple checklist for beginners.

Chapter: Architecture deep dive
  • Understanding data distribution: DHT.
  • Rendezvous hashing
  • Replication
  • Master-Slave replication
  • Peer-to-peer replication
  • Apache Ignite Memory-Centric storage
  • Apache Ignite Durable memory architecture
  • Write-Ahead-Log (WAL)
  • Baseline topology

The guide is available for free download. Moreover, you can clone or download the source code for the book from Github. The Apache Ignite quick start guide or the sample chapter covers Ignite version 2.6 and above. Do not hesitate to ask any questions if you will have any difficulties with the source code. For more details and advanced topics about Ignite, you can purchase the full book — happy reading.
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

Quick start with In memory Data Grid, Apache Ignite

UP1: For complete quick start guide, see also the sample chapter of the book "High performance in-memory computing with Apache Ignite" here . Even you can find the sample examples from the GitHub repository . IMDG or In memory data grid is not an in-memory relational database, an NoSQL database or a relational database. It is a different breed of software datastore. The data model is distributed across many servers in a single location or across multiple locations. This distribution is known as a data fabric. This distributed model is known as a ‘shared nothing’ architecture. IMDG has following characteristics: All servers can be active in each site. All data is stored in the RAM of the servers. Servers can be added or removed non-disruptively, to increase the amount of RAM available. The data model is non-relational and is object-based.  Distributed applications written on the platform independent language. The data fabric is resilient, allowing non-disruptive au...
Post a Comment
Read more

Analyse with ANT - a sonar way

After the Javaone conference in Moscow, i have found some free hours to play with Sonar . Here is a quick steps to start analyzing with ANT projects. Sonar provides Analyze with ANT document to play around with ANT, i have just modify some parts. Here is it. 1) Download the Sonar Ant Task and put it in your ${ANT_HOME}/lib directory 2) Modify your ANT build.xml as follows: <?xml version = '1.0' encoding = 'windows-1251'?> <project name="abc" default="build" basedir="."> <!-- Define the Sonar task if this hasn't been done in a common script --> <taskdef uri="antlib:org.sonar.ant" resource="org/sonar/ant/antlib.xml"> <classpath path="E:\java\ant\1.8\apache-ant-1.8.0\lib" /> </taskdef> <!-- Out-of-the-box those parameters are optional --> <property name="sonar.jdbc.url" value="jdbc:oracle:thin:@xyz/sirius.xyz" /> <property na...
Post a Comment
Read more