My workspace

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 Da...

A new version of using Hibernate OGM described in the  The Apache Ignite book . If it got you interested, check out the rest of the book for more helpful information. Often the first step to developing an Enterprise information system is creating the domain model, that is, listing the entities in the domain and defining the relationships between them. A domain model is a conceptual image of the problem your system is trying to solve. Domain model elements can be linked by relationships. Usually, relational objects are represented in a tabular format, while application object model are represented in an interconnected graph of the object format. While storing and retrieving an object model from the relational database, a few mismatch occurs such as Granularity, SubTypes etc. To solve the mismatches between relational and object model, JPA provides a collection of APIs and methods to manipulates with the persistence store. The JPA specification only defines relational database a...

Black Friday discount on High-performance in-memory computing with Apache Ignite. 40% discount https://leanpub.com/ignite/c/MKU2EsYCj6nN

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...

In this article, author of the book "High Performance in-memory computing with Apache Ignite" , will discuss the complex event processing with Apache Strom and the Apache Ignite. Part of this article taken from the complex event processing chapter of the book . There is no broadly or highly accepted definition of the term Complex Event Processing or CEP. What Complex Event Processing is may be briefly described as the following quote from the Wikipedia: "Complex Event Processing, or CEP, is primarily an event processing concept that deals with the task of processing multiple events with the goal of identifying the meaningful events within the event cloud. CEP employs techniques such as detection of complex patterns of many events, event correlation and abstraction, event hierarchies, and relationships between events such as causality, membership, and timing, and event-driven processes." For simplicity, Complex Event Processing (CEP) is a technology for low-laten...

Being author is fun, my first book is going to be published in the end of this year. For now, a sample chapter is available for download .

UPD1: This blog has been published in Java Dzone https://dzone.com/articles/pitfalls-of-the-mybatis-caches-with-apache-ignite UPD2: This blog also published in Habrahabr for Russian reader https://habrahabr.ru/company/at_consulting/blog/280452 UPD3: See also the sample chapter of the book "High performance in-memory computing with Apache Ignite" here . A week ago, MyBatis and Apache ignite announced of support apache ignite as a MyBatis cache (L2 cache). technically MyBatis support two levels of Caches: Local cache, which is always enable by default L2 cache, optional As Apache Ignite project is fast growing with it's various functionality, in this blog post we are going to examine the MyBatis support in some details. The second level cache stores the entity data, but NOT the entities or objects themselves. The data is stored in a 'serialised' format which looks like a hash map where the key is the entity Id, and the value is a list of primitive value...