Apache ignite--New Generation Database Cache system

Apache ignite--New Generation Database caching system Apache Ignite is a universal database caching system that supports not only all underlying database systems, such as RDBMS, NoSQL, and HDFs, Optional features such as Write-through and read-through, Write-behind caching are also supported.

"Editor's note" The rapid growth of data requires a lot of storage, the management of these data is not an easy task. But how to deal with data is a real challenge for developers compared to storage and management. Storage and processing of terabytes of data often causes developers to fall into a dilemma of speed, scalability, and overhead. Recently, Dmitriy Setrakyan in Dzone wrote, for everyone introduced the next Generation Database cache system Apache Ignite, compiled by ONEAPM engineers.

The following is the translation

Storing data in the cache can significantly increase the speed of your application, because caching can reduce the frequency of data being transmitted in your application and database. Apache ignite allows users to store common hot data in memory, which supports both sharding and replication, allowing developers to distribute data evenly across the cluster's hosts. At the same time, ignite supports any underlying storage platform, whether RDBMS, NoSQL, or HDFs.

After the cluster is configured, the dataset increases simply by adding nodes to the Ignite cluster without restarting the entire cluster. The number of nodes can be infinitely increased, so the ignite extensibility is infinite. Here are a few options to choose from in the Ignite configuration:

Write-through and Read-through

In Write-through mode, data updates in the cache are updated synchronously to the database. Read-through means that the requested data is automatically pulled from the database when it is not available in the cache.

Write-behind Caching

Ignite also provides a database asynchronous update pattern called Write-behind caching. By default, every update in Write-through initiates a request to the database. If you write with Write-behind caching, updates to the cache are consolidated into batches and then sent to the database. This can achieve considerable performance gains for frequently deleted applications.

Automating persistent data

Ignite provides an easy-to-use schema mapping tool so that the system can be automatically integrated with the database. This tool can automatically connect to the database and generate all the required XML or-mapping configurations as well as the Java domain Model POJOs.

SQL query

Querying the ignite cache is simple, using standard SQL. Ignite supports all SQL functions, aggregations, and group operations, and even supports distributed SQL JOINs. An example of SQL query in the following ignite:

Ignitecache<long, person> cache = Ignite.cache ("Mycache");//' Select ' query to concatenate the first and last name O f All persons. Sqlfieldsquery sql = new Sqlfieldsquery (  "Select Concat (FirstName,", LastName) from ");//Execute the query O n Ignite Cache and print the result.try (querycursor<list<?>> cursor = cache.query (sql)) {for  (list<?& Gt Row:cursor)    System.out.println ("Full name:" + row.get (0));}

Summary

Apache Ignite is an open source project focused on distributed memory computing that stores data in memory and distributes it across multiple nodes to provide fast data access. In addition, the option to synchronize data to the cache layer is also a big advantage. Finally, you can support any underlying database storage that also makes ignite a database cache first.

For more information, documentation, examples, please visit Apache Ignite official website.

Original link: Apache Ignite for Database Caching

Apache ignite--New Generation Database Cache system