The deployment process for Cassandra looks something like this: This template also has more Database Type options, including Snowflake and Cassandra. Liquibase - Run Command is more flexible and has implemented many of the commands available for the Liquibase product. However, this template only contained a fraction of what the Liquibase product is capable of and has been replaced with Liquibase - Run Command. In previous posts, the Liquibase - Apply changeset template was used to perform updates to databases. If you're new to Octopus, consider reading our getting started documentation to familiarize yourself with these concepts. This post assumes you know how to create Octopus projects and add steps to the deployment process. In this post, you use a build server or the Octopus command line interface (CLI) to package the dbchangelog.xml file into a. The Cassandra folder contains an XML file that has been built for use with Liquibase products to create the tables in the keyspace.

The Sakila project contains examples of deploying the Sakila database to different database servers using different database deployment technologies. This post uses the Sakila sample project. This post shows you how to deploy database changes to a Cassandra server using Octopus Deploy and Liquibase. Increasingly, however, we are hearing customers talk about Cassandra. Names like MongoDB, Couchbase, Azure Cosmos DB, and Amazon DynamoDB are some of the most recognizable names of NoSQL implementations. NoSQL continues to be a disruptor in the database world.

Tableplus cassandra