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

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

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

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