Software Alternatives, Accelerators & Startups

ProxySQL VS Liquibase

Compare ProxySQL VS Liquibase and see what are their differences

ProxySQL logo ProxySQL

ProxySQL: high-performance, GPL licensed MySQL proxy. It supports hundreds of thousands of concurrent connections and can be multiplexed to hundreds of servers.

Liquibase logo Liquibase

Database schema change management and release automation solution.
  • ProxySQL Landing page
    Landing page //
    2023-05-23
  • Liquibase Landing page
    Landing page //
    2023-08-04

ProxySQL videos

#ProxySQL Use Case Scenarios - #ProxySQL #Database Tutorial - René Cannaò - #Percona Live 2017

More videos:

  • Review - ProxySQL Use Case Scenarios / Alkin Tezuysal (Percona)
  • Review - Inexpensive Datamasking for MySQL with ProxySQL - data anonymization for developers

Liquibase videos

Version based database migration with Liquibase

More videos:

  • Review - Automated database updates (with LiquiBase and FlyWay) @ Baltic DevOps 2015
  • Review - Flyway vs. Liquibase

Category Popularity

0-100% (relative to ProxySQL and Liquibase)
MySQL Tools
20 20%
80% 80
Databases
28 28%
72% 72
Development
0 0%
100% 100
Database Management
100 100%
0% 0

User comments

Share your experience with using ProxySQL and Liquibase. For example, how are they different and which one is better?
Log in or Post with

Social recommendations and mentions

Based on our record, ProxySQL should be more popular than Liquibase. It has been mentiond 10 times since March 2021. We are tracking product recommendations and mentions on various public social media platforms and blogs. They can help you identify which product is more popular and what people think of it.

ProxySQL mentions (10)

  • Save Cost on RDS Data Transfer - Internet - Out
    Another option could be ProxySQL, where you can cache queries on the ProxySQL server. Source: about 1 year ago
  • Is replication between v5.1 and v8 possible?
    Also, if you're not using it yet, I can recommend looking at ProxySQL to do your read-write/read-only failover controls. Source: over 1 year ago
  • SSL Termination for SQL
    What are the recommendations here? I took a look into ProxySQL and it looks like since v2, it can do frontend and backend SSL connections. I have it locally working on a docker setup. Source: over 1 year ago
  • Business complexity with performance
    DB: Split you write-read operations. You may scale read as needed. Write operations can be slow if you have too many indices, so make sure to use only the ones you really need. Your DBMS may have some configuration to optimise, for example in MySQL if you do NOT need ACID compliance you can set innodb_flush_log_at_trx_commit = 2 to achieve better write speed. For MySQL you should also look into https://proxysql.com/. Source: over 1 year ago
  • Advanced caching mechanisms using distributed locks and async pub/sub systems.
    A Layer-7 Database Load Balancer is optional here. An L7-DBLB can be used for various use cases (eg: ProxySQL). One or more database instances handle queries from the web server. A Client-side DB query/connection load balancing can also be used instead of an L7-DBLB according to the use case of the application. - Source: dev.to / almost 2 years ago
View more

Liquibase mentions (5)

  • How do you guys go about the persistence layer?
    As far as keeping track of domain changes you can store DDL files in version control like you mention or use tools like Flyway (https://flywaydb.org) or Liquidbase (https://liquibase.org) which takes care of database migrations. Source: about 2 years ago
  • How do you guys go about the persistence layer? (x-post)
    I just use SQL directly (or something like JOOQ). For database migrations I use Liquibase. Source: about 2 years ago
  • Where questioning the scale of a company and its clients its seen bad
    Regarding the migrations, there are tools such as https://liquibase.org/ or FlyAway that handle this. Heck, you can even use an ORM that has a migration baked-in but that defeats the purpose of having the migrations in a separate project. Source: about 2 years ago
  • State based change management tool for Snowflake
    I've trialled schemachange and liquibase which are change script based tools. I've ruled out a whole load of other tools that are either change script based tools or don't support Snowflake, including the following:. Source: over 2 years ago
  • Learning SQL and using dll (CREATE,DROP,ALTER)
    Nowadays I prefer to automate database updates and deployment, using Liquibase and its relational database vendor agnostic syntax for that. Especially on production systems. But on local dev environments, I can still use the occasional SQL in a pinch. Source: over 2 years ago

What are some alternatives?

When comparing ProxySQL and Liquibase, you can also consider the following products

Gonarch Tech - MySQL High Availability as a service

Flyway - Flyway is a database migration tool.

MariaDB MaxScale - We are the company behind #MariaDB, the fastest growing #opensource #database. Download MariaDB at https://t.co/DtYwuH0FOl.

Slick - A jquery plugin for creating slideshows and carousels into your webpage.

PostgREST - Automatic REST API for Any Postgres Database

DBeaver - DBeaver - Universal Database Manager and SQL Client.