Liquibase vs MariaDB

Need advice about which tool to choose?Ask the StackShare community!


+ 1

+ 1
Add tool

Liquibase vs MariaDB: What are the differences?

Developers describe Liquibase as "Source control for your database". Developers store database changes in text-based files on their local development machines and apply them to their local databases. Changelog files can be be arbitrarily nested for better management. On the other hand, MariaDB is detailed as "An enhanced, drop-in replacement for MySQL". 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.

Liquibase belongs to "Database Tools" category of the tech stack, while MariaDB can be primarily classified under "Databases".

Some of the features offered by Liquibase are:

  • Supports code branching and merging
  • Supports multiple developers
  • Supports multiple database types

On the other hand, MariaDB provides the following key features:

  • Replication
  • Insert Delayed
  • Events

"Great database tool" is the primary reason why developers consider Liquibase over the competitors, whereas "Drop-in mysql replacement" was stated as the key factor in picking MariaDB.

Liquibase and MariaDB are both open source tools. MariaDB with 2.82K GitHub stars and 864 forks on GitHub appears to be more popular than Liquibase with 1.78K GitHub stars and 1.09K GitHub forks.

nrise, Docplanner, and MAK IT are some of the popular companies that use MariaDB, whereas Liquibase is used by Viadeo, Orbitz, and Virgin Pulse. MariaDB has a broader approval, being mentioned in 496 company stacks & 461 developers stacks; compared to Liquibase, which is listed in 15 company stacks and 12 developer stacks.

Advice on Liquibase and MariaDB
Maxim Ryakhovskiy
Needs advice

Hi all. I am an informatics student, and I need to realise a simple website for my friend. I am planning to realise the website using Node.js and Mongoose, since I have already done a project using these technologies. I also know SQL, and I have used PostgreSQL and MySQL previously.

The website will show a possible travel destination and local transportation. The database is used to store information about traveling, so only admin will manage the content (especially photos). While clients will see the content uploaded by the admin. I am planning to use Mongoose because it is very simple and efficient for this project. Please give me your opinion about this choice.

See more
Replies (7)
at Meam Software Engineering Group · | 4 upvotes · 64.6K views

Your requirements seem nothing special. on the other hand, MongoDB is commonly used with Node. you could use Mongo without defining a Schema, does it give you any benefits? Also, note that development speed matters. In most cases RDBMS are the best choice, Learn and use Postgres for life!

See more

The use case you are describing would benefit from a self-hosted headless CMS like contentful. You can also go for Strapi with a database of your choice but here you would have to host Strapi and the underlying database (if not using SQLite) yourself. If you want to use Strapi, you can ease your work by using something like PlanetSCaleDB as the backing database for Strapi.

See more
Nutchanon Ninyawee

SQL is not so good at query lat long out of the box. you might need to use additional tools for that like UTM coordinates or Uber's H3.

If you use mongoDB, it support 2d coordinate query out of the box.

See more
Tarun Batra
Back End Developer at instabox · | 2 upvotes · 57.4K views

MongoDB and Mongoose are commonly used with Node.js and the use case doesn't seem to be requiring any special considerations as of now. However using MongoDB now will allow you to easily expand and modify your use case in future.

If not MongoDB, then my second choice will be PostgreSQL. It's a generic purpose database with jsonb support (if you need it) and lots of resources online. Nobody was fired for choosing PostgreSQL.

See more

Any database will be a great choice for your app, which is less of a technical challenge and more about great content. Go for it, the geographical search features maybe be actually handy for you.

See more
Václav Hodek
CEO, lead developer at Localazy · | 1 upvotes · 57.8K views

Any database engine should work well but I vote for Postgres because of PostGIS extension that may be handy for travel related site. There's nothing special about your requirements.

See more
Ruslan Rayanov

Hi, Maxim! Most likely, the site is almost ready. But we would like to share our development with you. This is a constructor for web application. With it, you can create almost any site with different roles which have different levels of access to information and different functionality. The platform is managed via sql. knowing sql, you will be able to change the business logic as necessary and during further project maintenance. We will be glad to hear your feedback about the platform.

See more
Decisions about Liquibase and MariaDB
Omran Jamal
CTO & Co-founder at Bonton Connect · | 4 upvotes · 217.3K views

We actually use both Mongo and SQL databases in production. Mongo excels in both speed and developer friendliness when it comes to geospatial data and queries on the geospatial data, but we also like ACID compliance hence most of our other data (except on-site logs) are stored in a SQL Database (MariaDB for now)

See more
Get Advice from developers at your company using Private StackShare. Sign up for Private StackShare.
Learn More
Pros of Liquibase
Pros of MariaDB
  • 17
    Great database tool
  • 14
    Many DBs supported
  • 9
    Easy setup
  • 6
    Database independent migration scripts
  • 3
    Database version controller
  • 3
    Unique open source tool
  • 1
    Supports NoSQL and Graph DBs
  • 149
    Drop-in mysql replacement
  • 100
    Great performance
  • 74
    Open source
  • 54
  • 44
    Easy setup
  • 15
    Easy and fast
  • 14
    Lead developer is "monty" widenius the founder of mysql
  • 6
    Also an aws rds service
  • 4
    Learning curve easy
  • 4
    Consistent and robust
  • 2
    Native JSON Support / Dynamic Columns
  • 1
    Real Multi Threaded queries on a table/db

Sign up to add or upvote prosMake informed product decisions

Cons of Liquibase
Cons of MariaDB
  • 3
    No vendor specifics in XML format - needs workarounds
  • 3
    Documentation is disorganized
    Be the first to leave a con

    Sign up to add or upvote consMake informed product decisions

    What is Liquibase?

    Liquibase is a leading open-source tool for database schema change management. Liquibase helps teams track, version, and deploy database schema and logic changes so they can automate their database code process with their app code process.

    What is 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.

    Need advice about which tool to choose?Ask the StackShare community!

    What companies use Liquibase?
    What companies use MariaDB?
    See which teams inside your own company are using Liquibase or MariaDB.
    Sign up for Private StackShareLearn More

    Sign up to get full access to all the companiesMake informed product decisions

    What tools integrate with Liquibase?
    What tools integrate with MariaDB?

    Sign up to get full access to all the tool integrationsMake informed product decisions

    What are some alternatives to Liquibase and MariaDB?
    It lets you regain control of your database migrations with pleasure and plain sql. Solves only one problem and solves it well. It migrates your database, so you don't have to worry about it anymore.
    Hibernate is a suite of open source projects around domain models. The flagship project is Hibernate ORM, the Object Relational Mapper.
    It is a standalone change management system with no opinions about your database engine, application framework, or development environment. Native scripting. Changes are implemented as scripts native to your selected database engine.
    It is a modern database query and access library for Scala. It allows you to work with stored data almost as if you were using Scala collections while at the same time giving you full control over when a database access happens and which data is transferred.
    Spring Data
    It makes it easy to use data access technologies, relational and non-relational databases, map-reduce frameworks, and cloud-based data services. This is an umbrella project which contains many subprojects that are specific to a given database.
    See all alternatives