BigchainDB vs MySQL

Overview

MySQL

Stacks129.6K

Followers108.6K

Votes3.8K

GitHub Stars11.8K

Forks4.1K

BigchainDB

Stacks27

Followers71

Votes0

GitHub Stars4.0K

Forks769

BigchainDB vs MySQL: What are the differences?

<BigchainDB vs. MySQL>

1. **Data Model**: BigchainDB is a NoSQL database that stores data as assets, transactions, and blocks which are immutable. In contrast, MySQL follows the relational database model, storing data in tables with rows and columns, allowing for complex relationships.
   
2. **Consensus Mechanism**: BigchainDB uses a Byzantine fault-tolerant consensus mechanism, where transactions are validated by a network of nodes. On the other hand, MySQL does not have a built-in consensus mechanism, relying on traditional methods for data validation and consensus.

3. **Scalability**: BigchainDB is designed for scalability with its blockchain architecture, allowing for high throughput and performance in decentralized applications. In comparison, MySQL may face limitations in scalability due to its traditional relational database design, especially in distributed environments.

4. **Transaction Speed**: BigchainDB offers faster transaction speeds as it leverages parallel processing and a distributed network for validating transactions. MySQL, while efficient for traditional queries and data manipulation, may not match the transaction speeds of BigchainDB in certain use cases.

5. **Data Security**: BigchainDB ensures data security through the immutability and transparency inherent in blockchain technology, making it tamper-proof and resistant to unauthorized changes. MySQL relies on security measures such as user authentication and access control, which may not provide the same level of data integrity as BigchainDB.

6. **Use Cases**: BigchainDB is well-suited for applications requiring provenance, supply chain management, and asset tracking due to its blockchain capabilities. MySQL, being a traditional relational database, is commonly used for structured data storage and retrieval in various applications.

In Summary, BigchainDB and MySQL differ in their data models, consensus mechanisms, scalability, transaction speeds, data security, and use cases.

Share your Stack

Help developers discover the tools you use. Get visibility for your team's tech choices and contribute to the community's knowledge.

View Docs

CLI (Node.js)

Manual

Advice on MySQL, BigchainDB

Kyle

Web Application Developer at Redacted DevWorks

Dec 3, 2019

Decidedon

PostGIS

While there's been some very clever techniques that has allowed non-natively supported geo querying to be performed, it is incredibly slow in the long game and error prone at best.

MySQL finally introduced it's own GEO functions and special indexing operations for GIS type data. I prototyped with this, as MySQL is the most familiar database to me. But no matter what I did with it, how much tuning i'd give it, how much I played with it, the results would come back inconsistent.

It was very disappointing.

I figured, at this point, that SQL Server, being an enterprise solution authored by one of the biggest worldwide software developers in the world, Microsoft, might contain some decent GIS in it.

I was very disappointed.

Postgres is a Database solution i'm still getting familiar with, but I noticed it had no built in support for GIS. So I hilariously didn't pay it too much attention. That was until I stumbled upon PostGIS and my world changed forever.

449k views449k

Comments

Ido

Mar 6, 2020

Decided

My data was inherently hierarchical, but there was not enough content in each level of the hierarchy to justify a relational DB (SQL) with a one-to-many approach. It was also far easier to share data between the frontend (Angular), backend (Node.js) and DB (MongoDB) as they all pass around JSON natively. This allowed me to skip the translation layer from relational to hierarchical. You do need to think about correct indexes in MongoDB, and make sure the objects have finite size. For instance, an object in your DB shouldn't have a property which is an array that grows over time, without limit. In addition, I did use MySQL for other types of data, such as a catalog of products which (a) has a lot of data, (b) flat and not hierarchical, (c) needed very fast queries.

575k views575k

Comments

Navraj

CEO at SuPragma

Apr 16, 2020

Needs adviceon

MySQL

PostgreSQL

I asked my last question incorrectly. Rephrasing it here.

I am looking for the most secure open source database for my project I'm starting: https://github.com/SuPragma/SuPragma/wiki

Which database is more secure? MySQL or PostgreSQL? Are there others I should be considering? Is it possible to change the encryption keys dynamically?

Thanks,

Raj

401k views401k

Comments

Detailed Comparison

MySQL	BigchainDB
The MySQL software delivers a very fast, multi-threaded, multi-user, and robust SQL (Structured Query Language) database server. MySQL Server is intended for mission-critical, heavy-load production systems as well as for embedding into mass-deployed software.	It is designed to merge the best of two worlds: the “traditional” distributed database world and the “traditional” blockchain world. With high throughput, low latency, powerful query functionality, decentralized control, immutable data storage and built-in asset support.
-	Decentralization; Immutability; Native Support of Multiassets; Byzantine Fault Tolerant (BFT); Low Latency; Traditional Stack
Statistics
GitHub Stars 11.8K	GitHub Stars 4.0K
GitHub Forks 4.1K	GitHub Forks 769
Stacks 129.6K	Stacks 27
Followers 108.6K	Followers 71
Votes 3.8K	Votes 0
Pros & Cons
Pros 800 Sql 679 Free 562 Easy 528 Widely used 490 Open source Cons 16 Owned by a company with their own agenda 3 Can't roll back schema changes	No community feedback yet
Integrations
No integrations available	Golang Python C++ Blockchain Wagyu

What are some alternatives to MySQL, BigchainDB?

MongoDB

MongoDB stores data in JSON-like documents that can vary in structure, offering a dynamic, flexible schema. MongoDB was also designed for high availability and scalability, with built-in replication and auto-sharding.

PostgreSQL

PostgreSQL is an advanced object-relational database management system that supports an extended subset of the SQL standard, including transactions, foreign keys, subqueries, triggers, user-defined types and functions.

Microsoft SQL Server

Microsoft® SQL Server is a database management and analysis system for e-commerce, line-of-business, and data warehousing solutions.

SQLite

SQLite is an embedded SQL database engine. Unlike most other SQL databases, SQLite does not have a separate server process. SQLite reads and writes directly to ordinary disk files. A complete SQL database with multiple tables, indices, triggers, and views, is contained in a single disk file.

Cassandra

Partitioning means that Cassandra can distribute your data across multiple machines in an application-transparent matter. Cassandra will automatically repartition as machines are added and removed from the cluster. Row store means that like relational databases, Cassandra organizes data by rows and columns. The Cassandra Query Language (CQL) is a close relative of SQL.

Memcached

Memcached is an in-memory key-value store for small chunks of arbitrary data (strings, objects) from results of database calls, API calls, or page rendering.

MariaDB

Started by core members of the original MySQL team, MariaDB actively works with outside developers to deliver the most featureful, stable, and sanely licensed open SQL server in the industry. MariaDB is designed as a drop-in replacement of MySQL(R) with more features, new storage engines, fewer bugs, and better performance.

RethinkDB

RethinkDB is built to store JSON documents, and scale to multiple machines with very little effort. It has a pleasant query language that supports really useful queries like table joins and group by, and is easy to setup and learn.

ArangoDB

A distributed free and open-source database with a flexible data model for documents, graphs, and key-values. Build high performance applications using a convenient SQL-like query language or JavaScript extensions.

InfluxDB

InfluxDB is a scalable datastore for metrics, events, and real-time analytics. It has a built-in HTTP API so you don't have to write any server side code to get up and running. InfluxDB is designed to be scalable, simple to install and manage, and fast to get data in and out.

Related Comparisons

BigchainDB vs MySQL: What are the differences?

<BigchainDB vs. MySQL>

1. **Data Model**: BigchainDB is a NoSQL database that stores data as assets, transactions, and blocks which are immutable. In contrast, MySQL follows the relational database model, storing data in tables with rows and columns, allowing for complex relationships.
   
2. **Consensus Mechanism**: BigchainDB uses a Byzantine fault-tolerant consensus mechanism, where transactions are validated by a network of nodes. On the other hand, MySQL does not have a built-in consensus mechanism, relying on traditional methods for data validation and consensus.

3. **Scalability**: BigchainDB is designed for scalability with its blockchain architecture, allowing for high throughput and performance in decentralized applications. In comparison, MySQL may face limitations in scalability due to its traditional relational database design, especially in distributed environments.

4. **Transaction Speed**: BigchainDB offers faster transaction speeds as it leverages parallel processing and a distributed network for validating transactions. MySQL, while efficient for traditional queries and data manipulation, may not match the transaction speeds of BigchainDB in certain use cases.

5. **Data Security**: BigchainDB ensures data security through the immutability and transparency inherent in blockchain technology, making it tamper-proof and resistant to unauthorized changes. MySQL relies on security measures such as user authentication and access control, which may not provide the same level of data integrity as BigchainDB.

6. **Use Cases**: BigchainDB is well-suited for applications requiring provenance, supply chain management, and asset tracking due to its blockchain capabilities. MySQL, being a traditional relational database, is commonly used for structured data storage and retrieval in various applications.

In Summary, BigchainDB and MySQL differ in their data models, consensus mechanisms, scalability, transaction speeds, data security, and use cases.

BigchainDB vs MySQL

Overview