Software Alternatives, Accelerators & Startups

Azure Traffic Manager VS Liquibase

Compare Azure Traffic Manager VS Liquibase and see what are their differences

Azure Traffic Manager logo Azure Traffic Manager

Microsoft Azure Traffic Manager allows you to control the distribution of user traffic for service endpoints in different datacenters.

Liquibase logo Liquibase

Database schema change management and release automation solution.
  • Azure Traffic Manager Landing page
    Landing page //
    2023-01-26
  • Liquibase Landing page
    Landing page //
    2023-08-04

Azure Traffic Manager videos

Azure Traffic Manager Vlog 1

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 Azure Traffic Manager and Liquibase)
Web Servers
100 100%
0% 0
MySQL Tools
0 0%
100% 100
Web And Application Servers
Development
0 0%
100% 100

User comments

Share your experience with using Azure Traffic Manager 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, Liquibase seems to be more popular. It has been mentiond 5 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.

Azure Traffic Manager mentions (0)

We have not tracked any mentions of Azure Traffic Manager yet. Tracking of Azure Traffic Manager recommendations started around Mar 2021.

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: over 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: over 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: over 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 Azure Traffic Manager and Liquibase, you can also consider the following products

nginx - A high performance free open source web server powering busiest sites on the Internet.

Flyway - Flyway is a database migration tool.

AWS Elastic Load Balancing - Amazon ELB automatically distributes incoming application traffic across multiple Amazon EC2 instances in the cloud.

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

Google Cloud Load Balancing - Google Cloud Load Balancer enables users to scale their applications on Google Compute Engine.

Sqitch - Sqitch is a standalone database change management application without opinions about your database engine, development environment, or application framework.