MySQL vs ObjectBox

Overview

MySQL

Stacks129.6K

Followers108.6K

Votes3.8K

GitHub Stars11.8K

Forks4.1K

ObjectBox

Stacks9

Followers20

Votes0

MySQL vs ObjectBox: What are the differences?

Introduction

MySQL and ObjectBox are two popular database management systems with different approaches and features. Understanding the key differences between the two can help in choosing the most suitable solution for specific requirements.

Scalability: MySQL is a traditional SQL database that follows a relational data model. It is suitable for handling large amounts of structured data with complex relationships. On the other hand, ObjectBox is a NoSQL database that uses an object-oriented approach to handle data. It is particularly designed for scenarios that require high-performance and rapid data synchronization between devices.
Performance: MySQL relies on complex query optimizations and indexing techniques to achieve satisfactory performance for large datasets. However, it may encounter performance limitations when handling extremely high write/read loads or frequent updates due to its ACID compliance and relational nature. ObjectBox, on the other hand, offers highly efficient data access and update operations. It uses an embedded model, avoiding network round-trip delays, and also employs advanced indexing techniques like ACID2 to ensure faster response times even in high-load scenarios.
Data Modeling: MySQL uses a flexible and powerful relational data model, allowing the definition of complex relationships between entities. It supports the use of SQL queries, joins, and transactions for managing and manipulating data. ObjectBox, on the other hand, follows an object-oriented data model that focuses on simplifying data modeling and persistence. It provides a schema-free approach and supports complex object graphs, eliminating the need for manual mapping between objects and tables.
Flexibility: MySQL offers a wide range of SQL functionalities, including support for advanced querying, constraints, views, and stored procedures. It provides the ability to define complex database schemas and relationships, making it suitable for complex and structured data scenarios. ObjectBox, being a NoSQL database, is highly flexible and schemaless. It allows dynamic modification of data structures and supports data evolution and migration without requiring schema changes.
Ease of Use: MySQL requires the definition of a database schema and understanding of SQL for managing and manipulating data. It requires additional set up and configuration, making it suitable for scenarios that require strong data consistency and integrity. ObjectBox, on the other hand, has a simpler and more intuitive API, making it easier to learn and use. It supports automatic schema generation, reducing the need for manual configuration and allowing rapid development and prototyping.
Platform Support: MySQL is a widely adopted open-source database management system that runs on various platforms and operating systems. It has extensive community support and a rich ecosystem of tools and frameworks. ObjectBox, on the other hand, is positioned as a mobile and edge computing-focused database. It supports various platforms such as Android, iOS, Linux, Windows, macOS, and IoT devices, making it suitable for scenarios that require offline-first, multi-device synchronization.

In summary, MySQL is a relational database management system suitable for complex structured data scenarios with strong data consistency requirements, whereas ObjectBox is a NoSQL database management system designed for high-performance, scalable, and schema-less data scenarios with a focus on mobile and edge computing.

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, ObjectBox

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	ObjectBox
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 for developers who look for performance and ease of use. We are committed to providing you with the easiest APIs for you to keep your code short and maintainable. No SQL under the hood-Simply faster. Unlike other databases, it has been built from the ground up using key-value storage instead of column storage. The resulting performance is 10x faster than the leading alternative, we welcome you to try it yourself. It is fast regardless of the amount of data or operating system you are using.
-	10x faster than any alternative; Reduces cloud costs up to 60%; Supports Linux, Windows, Mac/iOS, Android, Raspbian, etc. Embedded or Containerized; Develop applications that work on- and offline, independently from a constant Internet connection, providing an “always-on”-feeling; Accelerate time-to-market, save development and lifecycle costs, save precious developer time for tasks that bring value
Statistics
GitHub Stars 11.8K	GitHub Stars -
GitHub Forks 4.1K	GitHub Forks -
Stacks 129.6K	Stacks 9
Followers 108.6K	Followers 20
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	Linux Android OS macOS iOS Windows Raspbian

What are some alternatives to MySQL, ObjectBox?

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

MySQL vs ObjectBox: What are the differences?

Introduction

Scalability: MySQL is a traditional SQL database that follows a relational data model. It is suitable for handling large amounts of structured data with complex relationships. On the other hand, ObjectBox is a NoSQL database that uses an object-oriented approach to handle data. It is particularly designed for scenarios that require high-performance and rapid data synchronization between devices.
Performance: MySQL relies on complex query optimizations and indexing techniques to achieve satisfactory performance for large datasets. However, it may encounter performance limitations when handling extremely high write/read loads or frequent updates due to its ACID compliance and relational nature. ObjectBox, on the other hand, offers highly efficient data access and update operations. It uses an embedded model, avoiding network round-trip delays, and also employs advanced indexing techniques like ACID2 to ensure faster response times even in high-load scenarios.
Data Modeling: MySQL uses a flexible and powerful relational data model, allowing the definition of complex relationships between entities. It supports the use of SQL queries, joins, and transactions for managing and manipulating data. ObjectBox, on the other hand, follows an object-oriented data model that focuses on simplifying data modeling and persistence. It provides a schema-free approach and supports complex object graphs, eliminating the need for manual mapping between objects and tables.
Flexibility: MySQL offers a wide range of SQL functionalities, including support for advanced querying, constraints, views, and stored procedures. It provides the ability to define complex database schemas and relationships, making it suitable for complex and structured data scenarios. ObjectBox, being a NoSQL database, is highly flexible and schemaless. It allows dynamic modification of data structures and supports data evolution and migration without requiring schema changes.
Ease of Use: MySQL requires the definition of a database schema and understanding of SQL for managing and manipulating data. It requires additional set up and configuration, making it suitable for scenarios that require strong data consistency and integrity. ObjectBox, on the other hand, has a simpler and more intuitive API, making it easier to learn and use. It supports automatic schema generation, reducing the need for manual configuration and allowing rapid development and prototyping.
Platform Support: MySQL is a widely adopted open-source database management system that runs on various platforms and operating systems. It has extensive community support and a rich ecosystem of tools and frameworks. ObjectBox, on the other hand, is positioned as a mobile and edge computing-focused database. It supports various platforms such as Android, iOS, Linux, Windows, macOS, and IoT devices, making it suitable for scenarios that require offline-first, multi-device synchronization.

MySQL vs ObjectBox

Overview

MySQL vs ObjectBox: What are the differences?