ArangoDB VS Liquibase

ArangoDB Reviews

Liquibase Reviews

ArangoDB mentions (3)

• How to choose the right type of database

  ArangoDB: A native multi-model database, it offers flexibility for documents, graphs, and key-values. This versatility makes it suitable for applications requiring a combination of these data models. - Source: dev.to / 2 months ago

• Spidergram is a collection of tools my company Autogram has built or enabled over the past several years to support our work to automate content inventories for large websites: it's part web crawler, part domain model, and part mad science. We released the first public beta today.

  ArangoDB, a "multi-modal" database engine that stores arbitrary JSON documents like MongoDB, key/value data like Redis, and graph relationships like Neo4j — and lets you leverage all three kinds of data in a single query. Source: over 1 year ago

• How do I install Arangodb with the default settings, without any questions to a user?

  I have a bash script and a part of it is installation of arangodb.com. I want a script to install Arangodb in such a way a user won't have select any options during installation, not even specify a password. I want it to have all the default settings, default password such as 1234, even an empty password will do, default config... Everything by default and without any questions to a user. Source: about 3 years ago

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: about 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