Deploy Cassandra on a Google Axion C4A virtual machine
Introduction
Get started with Cassandra on Google Axion C4A
Create a Google Axion C4A Arm virtual machine
Install Apache Cassandra
Test Cassandra baseline functionality
Benchmark Cassandra performance
Next Steps

  Log an issue

  Fork and edit

  Discuss on Discord

About this Learning Path

Skill level:  Introductory
Reading time:  30 min
Last updated:  09 Sep 2026
Skill level:
  Introductory
Reading time:
  30 min
Last updated:
  09 Sep 2026
Author:Pareena Verma, Arm
Arm IP:Neoverse
Tags: Databases Google Axion Linux Apache Cassandra Java cqlsh cassandra-stress
Author:
  • Pareena Verma, Arm
Arm IP:
Neoverse
Tags:
Databases Google Axion Linux Apache Cassandra Java cqlsh cassandra-stress

Who is this for?

This is an introductory topic for software developers migrating Cassandra workloads from x86_64 to Arm-based servers, specifically on Google Cloud C4A virtual machines built on Axion processors.

What will you learn?

After completing this Learning Path, you'll be able to perform the following tasks:

  • Provision an Arm-based SUSE SLES virtual machine on Google Cloud (C4A with Axion processors)
  • Install and configure Apache Cassandra on a SUSE Arm64 (C4A) instance
  • Validate Cassandra functionality using CQLSH and baseline keyspace/table operations
  • Benchmark Cassandra performance using cassandra-stress for read and write workloads on Arm64 (Aarch64) architecture

Prerequisites

Before starting, you'll need the following prerequisites:

Summary

AI-assisted

This summary was drafted with an approved AI-assisted workflow and reviewed by Arm contributors before publication. Human technical review remains part of the process so the final page reflects engineering rigor, accuracy, and Arm editorial standards.

Close
?
You’ll deploy Apache Cassandra on Arm-based Google Cloud Axion C4A virtual machines and validate a working baseline before running sample workload tests. First, you’ll create a c4a-standard-4 instance in the Google Cloud console and install Cassandra on Ubuntu or SUSE. Then, you’ll start Cassandra as a background service, with logs tailed to confirm “Startup complete,” followed by nodetool status to verify the node state. By the end, you’ll benchmark using the built-in cassandra-stress utility to exercise write, read, and mixed operations on Arm to confirm Cassandra is operating correctly.
Next