Triple, mainly represented by RDF with SPARQL as its query language. In TripleStore, data is represented as Subject-Predicate-Object. The database for this kind of data is usually called TripleStore. An example of TripleStore is BlazeGraph. - Source: dev.to / over 2 years ago

I think the best open-source graphdb, also used for Amazon Neptune, is blazegraph [1] For true data interoperability, as opposed to the silo data models required for property graph databases, the RDF w3c standard with SPARQL [2] is the industry standard. The new global API made possible with the Solid project [3] by Tim Berners-lee uses RDF [1] https://blazegraph.com/. - Source: Hacker News / 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