Profile cover photo
Profile photo
We provide services to support your Cassandra and Kafka deployments in the AWS cloud. Get up to speed fast. Prod Support. Multi-AZ/Region
We provide services to support your Cassandra and Kafka deployments in the AWS cloud. Get up to speed fast. Prod Support. Multi-AZ/Region

Cloudurable's interests
View all
Cloudurable's posts

Post has attachment
Check out our new CXO guide: Advantages of using Cloudurable™

(Cloudurable Cassandra Kafka AWS DevOps Support)

Our mission is to help you keep costs low in the cloud without compromising stability or security. We customize the initial setup to achieve optimal performance for your workloads. We streamline the DevOps process for Cassandra running in Amazon Web Services (AWS)/EC2. We provide a cost-efficient way to maximize your deployments tailored to your business needs.

Post has attachment
Watchdogs for non-stop Cassandra:

For rock solid reliability and resilience, Cloudurable™ Cassandra EC2 instances are started and monitored by the systemd watchdog service. The systemd watchdog ensures that the Cassandra service is running and if it stops running, the systemd system will restart Cassandra.

The key point here is the watchdogs automatically restarts Cassandra if the JVM ever exits or crashes. If you want to stop Cassandra, you need to tell the systemd (sudo systemctl stop cassandra ) to stop the instance. The watchdog system is really the one built into the OS. The systemd system provides full support for supervisor (software) watchdog support for individual system services. Since we configure Cassandra as a systemd service we get this watchdog support.

Since we repeat the journald logs (journald is part of systemd) to AWS CloudWatch, any restarts are automatically recorded, and we can create alerts and or remediate actions that handles these. Knowing your instances are restarting due to bugs, anomalies, or other problems is a very important KPI.

BUT WHY? How is this a benefit if Cassandra already has replication and resilience built in?

Why you need a watchdog:

Cassandra is likely at the heart of your microservices operational data storage needs. You might have a Cassandra Keyspace per microservice and you might have five or six microservices talking to 6 Keyspaces.

What if those microservices start getting 2 or 3x more traffic than normal?
What if there is a denial of service attack?
What if there is just a bug that got past the load testing regressions test of a new version of a new microservice?
Or worse what if there are just catastrophic anomalies?

Post has attachment
Benefits of Subscription Cassandra Support

Cassandra subscription support is just one of the services that Cloudurable™ provides. Our Subscription Cassandra Support pricing is very simple and affordable and scales up as your needs scale up which makes it easy to get started with Cassandra running in EC2 while not breaking your budget.

Cloudurable™ provides images (AMIs) and utilities to build images that have the following features.

* Integration with AWS metrics
* Integration with AWS alerting
* Easily deploy and resize EC2 instances without manually changing config
* Utilities to aid in configuration and cluster formation / deployment
* Installed AWS and Cassandra utilities to aid in backing up Cassandra to S3 and Glacier, taking EBS volume snapshots, and other administrative tasks.
* Configuring watchdogs to restart Cassandra if the Cassandra process dies

Images contain the following software components:

* Ergonomic cloud configuration™ of Cassandra based on the size of the EC2 image (adjusts for memory, CPU cores, disks attached).
* systemd service daemon that sends operating system KPIs to Amazon CloudWatch.
* systemd journald daemon log forwarder to send operating systems logs to Amazon CloudWatch
* systemd logstash forwarder to send Cassandra logs to Amazon CloudWatch Logs
* systemd Cassandra KPI daemon to send Cassandra KPIs to Amazon CloudWatch Metrics
configure Cassandra as a systemd service daemon with a watchdog (restarts if Cassandra crashes)
* Enterprise Level Support Only - configures advanced watchdog and health check system that can detect failures and remediate problems.

Post has attachment

Setting Up a Cassandra Cluster With SSL.

If compliance and security are a concern, you can set up Cassandra clusters with encryption in mind using SSL while ensuring nodes can still communicate with each other.
Cassandra allows you to secure the client transport (cqlsh) as well as the cluster transport cluster transport (storage transport). This article shows you how to set that up.

Post has attachment
Cloudurable Architecture Analysis Quickstart Services Package

The Cloudurable Architecture Analysis Quickstart Services Package is designed to prepare your team to launch Cassandra or Kafka in AWS/EC2. This services package provides focused architectural analysis on how to design, deploy, configure, monitor and support Cassandra or Kafka in AWS/EC2.

We provide the same Architecture Analysis for Kafka or Cassandra running in AWS.

The objective are:

Avoid costly mistakes
Pick the right EC2 instances
Use the right AWS tools for a fault tolerant fast system
Avoid wasting money on over provisioning AWS EC2

Post has attachment
Setting Up a Cassandra Cluster With Vagrant
New DZone Article.

Vagrant is easier to work with systemd services than Docker, so when it comes to provisioning and testing Cassandra clusters, Vagrant is the way to go.
The cassandra-image (on GitHub) project creates CentOS 7/Cassandra images for Docker, VirtualBox/Vagrant and AWS/EC2 using best practices for Cassandra OS setup and utilities to auto-configure Cassandra based on the ergonmics of the environment.

Post has attachment

Post has attachment
Cassandra Course -
Learn Cassandra to deliver successful prod apps from experts at Cloudurable

We are working on a new EC2 AMI and Docker image that uses centOS7, systemd, cloudwatch logging & metrics.

Post has attachment
Wait while more posts are being loaded