Takamaka "Caching server" enables PostgreSQL on Blockchain

Takamaka introduces in the primary architecture a type of node, called Caching Server. This is a client, i.e., a simplified node, which has an open source, high-availability relational databases management system inside it, example Postgresql.

Caching server is a "frontline" server, which allows nodes to expedite and take charge of all requests coming from the network, as well as transactions, key reading, query creation and more, quickly producing responses.

In fact, one will be able to query the Blockchain, and get " quick " answers, create complex SQL queries directly on the Blockchain and return data exactly as on classic relational db; even inexperienced users will be able to build the equivalent of an "Etherscan" by simply connecting to the Caching server, and extracting the data they need.

This solution integrates data points and easily creates customer-facing APIs, gaining efficiency and speed from the wallet, with a significant reduction in wait time.

You will be able to query data in blockchain, as on a native SQL db, allowing quick access to information and easier understanding of the underlying concepts.

Caching server synchronizes up to 5 EPOCHs simultaneously and provides for open source relational database at its core

Caching server simultaneously synchronizes up to 5 EPOCHs daily, reads at least 1.38 blocks in just 1 sec. with a significant reduction from the current Block read ( currently 30 sec.)

While keeping the time and duration of an EPOCH unchanged, the new client allows for faster synchronization of nodes on the blockchain.

The new client performs parallel operations of a large number of shares ( at least 70 percent ) without waiting for the blockchain state, making 100 percent use of CPU capabilities during the synchronization phase.

The parallelism of processes, capable of giving the client a remarkable speed of action and the ability to process an impressive amount of data from the Blockchain, was made possible by the integration of Webflux, a reactive-stack web framework, capable of fully supporting non-blocking Web Application development, i.e., each call is a non-blocking and asynchronous flow within the application.

Thanks to this solution, the uploading of blocks, is no longer done sequentially, which as a current consequence creates "long" waiting times, but on the contrary Caching server allows the insertion of even 50 blocks in one go, simultaneously updating the state of the DB and at the same time allowing a linear evaluation of the collected value of the data.

The 'data insertion takes place in a massive manner and with a large number of parallel processes, without the need to wait for the state of the Blockchain and while on the one hand such operations evaluate the algorithm, signatures, hashes, and invalid tx, on the other hand their evaluation is done separately.

This solution allows new, unsynchronized or lagging nodes to join the network and arrive at full synchronization in a very short time, allowing an improvement in general terms of the performance of the entire network.

With the new client, the Takamaka network is now a constantly synchronized, more stable and secure network.

FORK without service interruption: born Caching server" enables PostgreSQL on the Blockchain

When and how will the new client be placed on the Takamaka network ?

Caching server is a Node that will replace all the Nodes on the Takamaka network, but in the first phase it will be used as a Support Server on which the exchanges will connect to, so that the exchanges will be able to give fast responses.

Later the Takamaka Explorer will point to Caching server improving performance and service.
 

The network upgrade will take place with the replacement of the current Nodes with the new Clients, which will replace them as soon as they are synchronized. 

This is a FORK that will happen soon and without service interruption.