I’m willing to bet that if you’re reading this article you’ve at least heard of MariaDB. Heck, maybe you’ve even used it at some point. But, if not, I highly recommend that you give it a quick glance as, at the highest level, it’s a pretty solid, free (yea, free) open-source database solution that you can use for anything from some lightweight tinkering to supporting fully-fledged, production-grade applications.
Tip: If you'd like to jump right into a MariaDB database and use the same dataset in this article be sure to check out this MariaDB JSON Quickstart Guide!
We utilize relational data models to improve database performance and allow users to recreate real-world relationships. The shipping and tracking app blueprint showcases these capabilities in action, with the help of custom codeless APIs.
App blueprints are more than just templates from which to build a specific type of application. We design all of our free App Blueprints to provide one or more key functions that a developer would want to add to their application, regardless of the app’s business use.
Editor’s Note: The following is an article written for and published in DZone’s 2021 Data Persistence Trend Report.
Reading about the death of the relational database seems like a regular occurrence. However, here we are in 2021, and the relational data store is going strong. If we look at the DB-Engines Ranking website, six of the top 10, including the top four spots, are all relational data stores. Evidently, structured, or relational, data storage is here to stay. Yet four of the top spots are held by non-relational engines. Could that mean that relational data storage is really dying?
In recent years, NoSQL distributed databases have become common, as they are built from the ground up to be distributed. Yet they force difficult design choices, such as choosing availability over consistency, data integrity, and ease of query, to meet their applications’ need for scale. This Refcard serves as a reference to the key characteristics of distributed SQL databases, how functionality compares across database offerings, and the criteria for designing a proof of concept.
In almost every industry, there is a digital transformation underway that is driven by IoT and Big Data. What’s important to recognize is that IoT isn’t about things; it’s about the data those things collect. Organizations rely on this data to provide better user experiences, to make smarter business decisions, and, ultimately, fuel their growth.
However, none of this is possible without a reliable database that is able to handle the massive amounts of data generated by IoT devices. Relational databases are known for being flexible, easy to work with, and mature. What they aren’t particularly known for is scale, which prompted the creation of NoSQL databases. As you may or may not already know, there are ways to overcome this disadvantage.
