Author: telemaco 2015-10-29 06:57:39
Published on: 2015-10-29T06:57:39+00:00
The proposal suggests having two options for Bitcoin node users: a default RocksDB/SQLite/LevelDB or an alternative option that allows users to connect to any other RDBMS using ODBC or JDBC. The traditional approach has been to use the open standard for database connectivity, but this limits users to slower databases. By allowing async disk writes or faster databases, users can benefit from increased speed and better data management.With this proposal, users would only need to have one machine with their Bitcoin node and an RDBMS client installed (such as SAP Sybase, Oracle, or Microsoft). The Bitcoin node would store data using the ODBC/JDBC protocol on any RDBMS installed in their organization, enabling them to take advantage of async and indexes and to use their already licensed and configured system of choice. This would make Bitcoin information available to thousands of software packages and programmers who work with RDBMS, not just "RocksDB" or some obscure database system.By outsourcing data management to the existing database world, users could easily create Bitcoin statistics, graphs, and analysis with existing software packages or connect Bitcoin data to their own sources. They could even analyze Bitcoin data on a data warehouse or any imaginable approach. However, every transaction would still have to go through the Bitcoin node, with only the data management being handled by the RDBMS side.
Updated on: 2023-06-11T00:38:31.279923+00:00