HN Showcase
Back to browse
GitHub Repository

casschange is purpose-built CQL migration tool for Apache Cassandra, Managed Cassandra, AstraDB and ScyllaDB.

1 starsPython

Cassachange – A migration tool for Cassandra, AstraDB and ScyllaDB

by cassachange·Mar 4, 2026·1 point·0 comments
Visit ProjectView on HN

AI Analysis

●●SolidNiche GemSolve My Problem

Cassandra schema migration tool addressing real AstraDB pain—but Flyway, Liquibase, and raw CQL dominate.

Strengths
  • •Solves genuine pain: CQL migrations across environments with state tracking, addressing the 'drift between environments' problem author mentions.
  • •Multi-platform support: works with Apache Cassandra, managed Cassandra, AstraDB (including SCB), and ScyllaDB.
  • •Thoughtful feature scope: migration tracking, data insights, and MCP integration for AI tooling context.
Weaknesses
  • •Niche audience limits impact: only relevant to Cassandra/ScyllaDB users, a shrinking category vs. PostgreSQL/MySQL.
  • •Unproven adoption: no public evidence of production use; Flyway and Liquibase already handle Cassandra migrations for years.
Target Audience

Backend engineers and DevOps teams managing Cassandra clusters in production or using AstraDB.

Similar To

Flyway · Liquibase

Post Description

I’ve been working with AstraDB recently, and it reminded me how painful Cassandra schema management can be — especially when handling CQL migrations across environments.

Most tools I tried either:

Assume simple linear migrations

Don’t work well with managed Cassandra setups

Or make it hard to understand the actual state of a cluster

So I built cassachange.

It supports:

Apache Cassandra Managed Cassandra AstraDB (including SCB) ScyllaDB

It handles schema migrations, but I also added data insights and MCP capabilities because understanding the current cluster state is often half the battle.

A few things I’m especially curious about:

How are people managing Cassandra schema changes in production today?

Are most teams still using raw CQL scripts?

How do you handle drift between environments?

Has anyone built internal tooling for this?

I’d love critical feedback — especially from people running Cassandra/Scylla at scale.

Docs: https://cassachange.com

Repo: https://github.com/sketchmyview/cassachange

Happy to answer anything.

Similar Projects