Nil Foundation

=nil; `DROP DATABASE * is a database management system which introduces database-level replication protocols and cluster commit log data structure, which, along with swappable storage engines and swappable query languages make it possible to handle very different database types within the same software instance

In particular, this enables =nil; `DROP DATABASE* to handle Bitcoin, Ethereum and any other fault-tolerant replication-enabled database as usual database within database management system, providing them with traditional DBMS-specific features: state sharding (master-slave state clusterization), query language (e g SQL-alike SELECTs and UPSERTs), inter-database queries and much more

Each database is capable of using its own storage engine, specific and most suitable to the internal data structure a particular database manages This means the replication and data management performance will not degrade no matter of the database data and replication protocol kind

A single database node is capable to handle more than a single cluster A single database limits those clusters to be of different types (e g fault-tolerant full-replica over Raft-sharded state) Separate, independent databases, being handled by a single node instance, do not set any limits on that

Merge Operators Control Data Mutations

Every node (or a cluster) state mutation is wrapped with merge operator Its purpose is to ensure proper incoming data merging into a state no matter of what kind the incoming mutation is - query-induced conditionally-accepted transaction or a replication-induced state mutation

Library-Level (Swappable) Query Languages

Query language implemented as a library with a common language (JS, C++, Rust, you name it) inside virtualization engine enables employment of the selected language ecosystem to combine it with data management capabilities This also means several query languages are possible to be enabled on top of the same node instance SQL-alike query language is available as well

Inter-database queries allow to query and modify the state of more than one database with a single query All the state mutations are going through the node (or a cluster) commit log (with merge operators), in case particular database has a replication already running, so such queries allow databases to query each others state without breaking a local storage (or some cluster) consistency

Each database is supposed to have a replication protocol which fits its data structure and purpose This means it is possible to run the cluster with authenticated commit log data structure (e g any database compying to Bitcoin replication protocol) along with running more traditional Raft-based cluster nearby or underneath the same (or a different one) database state