Skip to main content

The Apache Ignite book

After a year, we have decided to write down another book related to the Apache Ignite distributed database. Within a year, Apache Ignite team redesigned the memory architecture and released a few new versions which cover new features such as Native persistence, baseline topology. Apache Ignite also optimized the performance of the SQL, added new features like Alter tables to DDL and also introduced SQLLINE command line tool for SQL based interaction. From this given release Apache Ignite team revisited the definition and purpose of the project. By their words, the definition "in-memory data fabrics/grids" limits its capabilities, rather than the distributed database, caching, and processing platform. So, in this book, we are going to cover the following topics:

  1. Apache Ignite architecture in details to build right solutions to given business problems.
  2. Use cases of using in-memory databases
  3. How Apache Ignite SQL works and how you can optimize the SQL engine to get better performance
  4. Developing applications with Spring Data/Hibernate OGM/MyBatis backed by Apache Ignite.
  5. How to use Apache Ignite compute grid as a low-latency software.
  6. Developing distributed microservice in fault-tolerant fashion.
  7. Processing continuously never-ending streaming data.
  8. Accelerate Big data ecosystem without changing any existing code.
  9. How to use Apache Ignite as a Cache as a Service to improve the performance of your applications. 


The target audience of this book will be IT architect, team leaders, a programmer with minimum programming knowledge.

No excessive knowledge is required, though it would be good to be familiar with JAVA and Spring framework. The book is also useful for any reader, who already familiar with Oracle Coherence, Hazelcast, Infinispan or Memcached. The release date of the book is not fixed yet, but we expect it in winter 2018.
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

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

Writing weblogic logs to database table

By default, oracle weblogic server logging service uses an implementation, based on the Java Logging APIs by using the LogMBean.isLog4jLoggingEnabled attribute. With a few effort you can use log4j with weblogic logging service. In the Administration Console, you can specify Log4j or keep the default Java Logging implementation. In this blog i will describe how to configure log4j with weblogic logging service and writes all the logs messages to database table. Most of all cases it's sufficient to writes log on files, however it's better to get all the logs on table to query on it. In our case we have 3 different web logic servers in our project and our consumer need to get all the logs in one central place to diagnose if something goes wrong. First of all we will create a simple table on our oracle database schema and next configure all other parts. Here we go: 1) CREATE TABLE LOGS (USER_ID VARCHAR2(20), DOMAIN varchar2(50), DATED DATE NOT NULL, LOGGER VARCHAR2(500) NOT...
Post a Comment
Read more