Dynobase.dev VS Liquibase

I use recommend taking a look at Dynobase, written by an AWS Dynamodb team affiliate and also https://retool.com/integrations/aws-dynamodb. Source: over 1 year ago

Have you seen Dynobase? https://dynobase.dev. - Source: Hacker News / over 2 years ago

There are reasonably better alternatives: - DynamoDB Workbench (free, AWS official): https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/workbench.html - Dynobase (paid, third-party): https://dynobase.dev/. - Source: Hacker News / over 2 years ago

Moreover, the ecosystem of DynamoDB is constantly growing. There are more and more tools providing useful abstractions like DynamoDB Toolbox by Jeremy Daly for working with single-table design, Dynamoose for ORM-like experience, AWS Amplify which hides the DynamoDB layer from the programmer completely, or Dynobase which helps you in navigating between profiles, regions, tables and exploring datasets. - Source: dev.to / almost 3 years ago

Making DynamoDB more accessible with Rafal Wilinski (Real World Serverless Podcast)— DynamoDB continues to grow in popularity, with how well it fits with serverless architectures, more and more companies are choosing to go with managed, highly-integrated, NoSQL database options like DynamoDB. In this podcast episode, Rafal talks through lots of things DynamoDB in his journey creating Dynobase, which is a DynamoDB... - Source: dev.to / almost 3 years ago

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

I just use SQL directly (or something like JOOQ). For database migrations I use Liquibase. Source: about 2 years ago

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

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

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