Get Advice Icon

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

Liquibase
Liquibase

99
93
+ 1
33
MariaDB
MariaDB

3.6K
2.6K
+ 1
472
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.

What is Liquibase?

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.

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.
Get Advice Icon

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

Why do developers choose Liquibase?
Why do developers choose MariaDB?

Sign up to add, upvote and see more prosMake informed product decisions

    Be the first to leave a con
    What companies use Liquibase?
    What companies use MariaDB?

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

    What tools integrate with Liquibase?
    What tools integrate with MariaDB?
      No integrations found

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

      What are some alternatives to Liquibase and MariaDB?
      Flyway
      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
      Hibernate is a suite of open source projects around domain models. The flagship project is Hibernate ORM, the Object Relational Mapper.
      Slick
      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.
      Sequel Pro
      Sequel Pro is a fast, easy-to-use Mac database management application for working with MySQL databases.
      PostGIS
      PostGIS is a spatial database extender for PostgreSQL object-relational database. It adds support for geographic objects allowing location queries to be run in SQL.
      See all alternatives
      Decisions about Liquibase and MariaDB
      StackShare Editors
      StackShare Editors
      MariaDB
      MariaDB
      MySQL
      MySQL

      Airbnb’s web experience is powered by a Rails monolith, called Monorail, that talks to several different Java services. MySQL databases store business data and are partitioned by functionality, with messages and calendar management, for example, stored separately from the main booking flow in their own databases.

      As traffic to the site continued growing, though, “one notable resource issue with MySQL databases [was] the increasing number of database connections from application servers.”

      Airbnb uses AWS’s Relational Database Service (RDS) to power their MySQL instances, and “RDS uses the community edition of MySQL server, which employs a one-thread-per-connection model of connection management.” With Airbnb’s scale, this meant that their databases would hit the C10K problem, which states that “there is an upper bound in the number of connections that MySQL server can accept and serve without dramatically increasing the number of threads running, which severely degrades MySQL server performance.”

      When an RDS MySQL server hits resource limits, users will have trouble connecting to the site.

      MySQL does have dynamic thread pooling, but it’s only available in the enterprise edition; AWS MySQL RDS, though, doesn’t offer this feature, meaning Airbnb didn’t have access to dynamic thread pooling out-of-the-box.

      After surveying several options, the team chose MariaDB MaxScale, which is “a MySQL database proxy that supports intelligent query routing in between client applications and a set of backend MySQL servers.”

      Instead of using the MariaDB MaxScale off-the-shelf, however, they decided to fork it and implement their own version that would include connection pooling. Other MaxScale features, like request throttling and query blocklisting were implemented as well.

      To enable horizontal scaling of the web application, the team deployed a MaxScale database proxy service in between app servers and MySQL servers. Through the service discovery system SmartStack, applications now “discover and connect to the database proxy service instead of the MySQL database,” allowing horizontal scaling to meet capacity demands.

      Additionally, new Airbnb MaxScale proxy server instances can be launched to further enable horizontal scaling.

      See more
      Amazon ElastiCache
      Amazon ElastiCache
      Amazon Elasticsearch Service
      Amazon Elasticsearch Service
      AWS Elastic Load Balancing (ELB)
      AWS Elastic Load Balancing (ELB)
      Memcached
      Memcached
      Redis
      Redis
      Python
      Python
      AWS Lambda
      AWS Lambda
      Amazon RDS
      Amazon RDS
      Microsoft SQL Server
      Microsoft SQL Server
      MariaDB
      MariaDB
      Amazon RDS for PostgreSQL
      Amazon RDS for PostgreSQL
      Rails
      Rails
      Ruby
      Ruby
      Heroku
      Heroku
      AWS Elastic Beanstalk
      AWS Elastic Beanstalk

      We initially started out with Heroku as our PaaS provider due to a desire to use it by our original developer for our Ruby on Rails application/website at the time. We were finding response times slow, it was painfully slow, sometimes taking 10 seconds to start loading the main page. Moving up to the next "compute" level was going to be very expensive.

      We moved our site over to AWS Elastic Beanstalk , not only did response times on the site practically become instant, our cloud bill for the application was cut in half.

      In database world we are currently using Amazon RDS for PostgreSQL also, we have both MariaDB and Microsoft SQL Server both hosted on Amazon RDS. The plan is to migrate to AWS Aurora Serverless for all 3 of those database systems.

      Additional services we use for our public applications: AWS Lambda, Python, Redis, Memcached, AWS Elastic Load Balancing (ELB), Amazon Elasticsearch Service, Amazon ElastiCache

      See more
      Joshua Dean Küpper
      Joshua Dean Küpper
      CEO at Scrayos UG (haftungsbeschränkt) · | 5 upvotes · 35.5K views
      atScrayos UG (haftungsbeschränkt)Scrayos UG (haftungsbeschränkt)
      Sentry
      Sentry
      GitLab
      GitLab
      PostgreSQL
      PostgreSQL
      MariaDB
      MariaDB

      We primarily use MariaDB but use PostgreSQL as a part of GitLab , Sentry and @Nextcloud , which (initially) forced us to use it anyways. While this isn't much of a decision – because we didn't have one (ha ha) – we learned to love the perks and advantages of PostgreSQL anyways. PostgreSQLs extension system makes it even more flexible than a lot of the other SQL-based DBs (that only offer stored procedures) and the additional JOIN options, the enhanced role management and the different authentication options came in really handy, when doing manual maintenance on the databases.

      See more
      Miguel Suarez
      Miguel Suarez
      Lead Developer · | 8 upvotes · 61.6K views
      atJobsrepublicJobsrepublic
      PostgreSQL
      PostgreSQL
      Liquibase
      Liquibase
      Flyway
      Flyway
      #Backwards-compatible
      #Migration

      Flyway vs Liquibase #Migration #Backwards-compatible

      We were looking for a tool to help us integrating the migration scripts as part of our Deployment. At first sight both tools look very alike, are well integrated with Spring, have a fairly frequent development activity and short release cycles.

      Liquibase puts a lot of emphasis on independence with the DB, allowing you to create the scripts on formats like JSON and YML, abstracting away from SQL, which it's also supported. Since we only work with one DB type across services we wouldn't take much advantage of this feature.

      Flyway on the other hand has the advantage on being actively working on the integration with PostgreSQL 11, for it's upcoming version 6. Provides a more extensive set of properties that allow us to define what's allowed on what's not on each different environment.

      Instead of looking for a tool that will allow us to rollback our DB changes automatically, we decided to implement backwards-compatible DB changes, for example adding a new column instead of renaming an existing one, postponing the deletion of the deprecated column until the release has been successfully installed.

      See more
      Interest over time
      Reviews of Liquibase and MariaDB
      Review ofMariaDBMariaDB

      MySQL was founded by Allan Larsson, Michael Widenius and David Axmark in the year 1995, 19 years ago. It was released under the name of co-founder Michael Widenius daughter, ‘My‘. This project was released under GNU General Public License as well as under certain Proprietary License. MySQL was owned by MySQL AB firm until it went into the hands of Oracle Corporation. It is written in Programming Language – C and C++ and is available for Windows, Linux, Solaris, MacOS and FreeBSD.

      In the year 2009, Michael Widenius started working on MarisDB as a fork of MySQL. In the year 2012 the bricks of nonprofit MariaDB Foundation was laid. It was named after the founder’s daughter Maria.

      MariaDB is a fork of MySQL Relational Database Management System which again is released under GNU General Public License. It is written in Programming Language – C, C++, Perl and Bash and is available for Systems Linux, Windows, Solaris, MacOS and FreeBSD.

      How developers use Liquibase and MariaDB
      Avatar of Scrayos UG (haftungsbeschränkt)
      Scrayos UG (haftungsbeschränkt) uses MariaDBMariaDB

      Aside from Redis, we use MariaDB to store long-term information like user-data and big-data like regeneration-information for our open-world servers. We extensively use the relational aspects of MariaDB in joins, nested queries and unions.

      Avatar of Seungkwon Park
      Seungkwon Park uses MariaDBMariaDB

      mysql보다 mariaDB가 join면에서 우수하다는 문서를 읽었습니다. 이 부분은 저의 블로그에서도 다뤘고 저의 word press 블로그는 mysql 대신 mariaDB 를 사용합니다.

      특히 limit 기능이 pagenation 처리를 할 때 너무 직관적이고 편해서 mariaDB, mysql을 사랑합니다.

      Avatar of Ana Phi Sancho
      Ana Phi Sancho uses MariaDBMariaDB

      Introduced in computer science course.managing relational database management systems, database analytics, and for data processing

      Avatar of nrise
      nrise uses MariaDBMariaDB

      수 백만개가 넘는 태그 키워드의 자동완성을 위해서 별도의 데이터베이스를 구축하였습니다. MariaDB 는 MySQL 을 포크한 프로젝트입니다. MySQL 과의 강력한 호환성을 지니며, 큰 튜닝 없이 강력한 성능을 보장합니다.

      Avatar of Dolls Kill
      Dolls Kill uses MariaDBMariaDB

      MariaDB has allowed us to easily scale out our DB cluster. Also has better replication tools than MySQL

      How much does Liquibase cost?
      How much does MariaDB cost?
      Pricing unavailable
      Pricing unavailable
      News about Liquibase
      More news