StackShareStackShare
Follow on
StackShare

Discover and share technology stacks from companies around the world.

Follow on

© 2025 StackShare. All rights reserved.

Product

  • Stacks
  • Tools
  • Feed

Company

  • About
  • Contact

Legal

  • Privacy Policy
  • Terms of Service
  1. Stackups
  2. Application & Data
  3. Databases
  4. Databases
  5. InfluxDB vs Scylla

InfluxDB vs Scylla

OverviewDecisionsComparisonAlternatives

Overview

InfluxDB
InfluxDB
Stacks1.0K
Followers1.2K
Votes175
ScyllaDB
ScyllaDB
Stacks143
Followers197
Votes8

InfluxDB vs Scylla: What are the differences?

Introduction

In this article, we will discuss the key differences between InfluxDB and Scylla, two popular database management systems. Both InfluxDB and Scylla have unique features and capabilities, making them suitable for different use cases. Let's explore the differences between these two databases.

  1. Data Structure: InfluxDB is a time-series database, optimized for storing and retrieving time-stamped data efficiently. It is designed to handle high write and query loads for time-based data. Scylla, on the other hand, is a NoSQL database that provides high scalability and low latency for real-time workloads. It is based on the Apache Cassandra project and is optimized for high availability and fault tolerance.

  2. Consistency Model: InfluxDB follows a strong consistency model, ensuring that queries return the most up-to-date data. It provides strict consistency for both reads and writes. In contrast, Scylla uses a tunable consistency model, allowing users to choose between stronger consistency or higher availability depending on their application requirements. It provides eventual consistency by default but can be configured for stronger consistency if needed.

  3. Query Language: InfluxDB uses its own query language called InfluxQL, which is specifically designed for time-series data analysis. It provides functions and operators tailored for analyzing time-based data efficiently. Scylla, on the other hand, uses Cassandra Query Language (CQL) for querying the database. CQL is a SQL-like language that supports a wide range of querying and indexing capabilities.

  4. Scaling: InfluxDB provides vertical scaling, meaning it can handle increased workloads by adding more resources to a single server. It can be scaled vertically by adding more CPU, memory, or storage to the existing server. Scylla, on the other hand, provides horizontal scaling, allowing users to add more nodes to the cluster to distribute the workload. It can handle massive amounts of data and high read and write loads by adding more machines to the cluster.

  5. Data Replication: InfluxDB supports continuous data replication across multiple servers to ensure high availability and fault tolerance. It uses a distributed consensus algorithm to replicate data and maintain consistency. Scylla also provides data replication for fault tolerance but uses a different approach. It uses a shared-nothing architecture where data is partitioned and replicated across multiple nodes, ensuring high availability and fault tolerance.

  6. Data Model: InfluxDB uses a tag-value data model, where each data point is associated with tags and values. Tags are indexed and used for efficient filtering and grouping of data. Scylla uses a column-based data model, where data is stored in columns rather than rows. This allows for efficient read and write operations, especially when dealing with large datasets.

In summary, InfluxDB is optimized for time-series data analysis, follows a strong consistency model, and uses a tag-value data model. On the other hand, Scylla is a NoSQL database optimized for high scalability, provides tunable consistency, and uses a column-based data model. These differences make them suitable for different use cases and application requirements.

Share your Stack

Help developers discover the tools you use. Get visibility for your team's tech choices and contribute to the community's knowledge.

View Docs
CLI (Node.js)
or
Manual

Advice on InfluxDB, ScyllaDB

Anonymous
Anonymous

Apr 21, 2020

Needs advice

We are building an IOT service with heavy write throughput and fewer reads (we need downsampling records). We prefer to have good reliability when comes to data and prefer to have data retention based on policies.

So, we are looking for what is the best underlying DB for ingesting a lot of data and do queries easily

381k views381k
Comments
Tom
Tom

CEO at Gentlent

Jun 9, 2020

Decided

The Gentlent Tech Team made lots of updates within the past year. The biggest one being our database:

We decided to migrate our #PostgreSQL -based database systems to a custom implementation of #Cassandra . This allows us to integrate our product data perfectly in a system that just makes sense. High availability and scalability are supported out of the box.

387k views387k
Comments
Vinay
Vinay

Head of Engineering

Sep 19, 2019

Needs advice

The problem I have is - we need to process & change(update/insert) 55M Data every 2 min and this updated data to be available for Rest API for Filtering / Selection. Response time for Rest API should be less than 1 sec.

The most important factors for me are processing and storing time of 2 min. There need to be 2 views of Data One is for Selection & 2. Changed data.

174k views174k
Comments

Detailed Comparison

InfluxDB
InfluxDB
ScyllaDB
ScyllaDB

InfluxDB is a scalable datastore for metrics, events, and real-time analytics. It has a built-in HTTP API so you don't have to write any server side code to get up and running. InfluxDB is designed to be scalable, simple to install and manage, and fast to get data in and out.

ScyllaDB is the database for data-intensive apps that require high performance and low latency. It enables teams to harness the ever-increasing computing power of modern infrastructures – eliminating barriers to scale as data grows.

Time-Centric Functions;Scalable Metrics; Events;Native HTTP API;Powerful Query Language;Built-in Explorer
High availability; horizontal scalability; vertical scalability; Cassandra compatible; DynamoDB compatible; wide column; NoSQL; lightweight transactions; change data capture; workload prioritization; shard-per-core; IO scheduler; self-tuning
Statistics
Stacks
1.0K
Stacks
143
Followers
1.2K
Followers
197
Votes
175
Votes
8
Pros & Cons
Pros
  • 59
    Time-series data analysis
  • 30
    Easy setup, no dependencies
  • 24
    Fast, scalable & open source
  • 21
    Open source
  • 20
    Real-time analytics
Cons
  • 4
    Instability
  • 1
    Proprietary query language
  • 1
    HA or Clustering is only in paid version
Pros
  • 2
    Replication
  • 1
    Fewer nodes
  • 1
    High performance
  • 1
    Written in C++
  • 1
    High availability
Integrations
No integrations available
KairosDB
KairosDB
Wireshark
Wireshark
JanusGraph
JanusGraph
Grafana
Grafana
Hackolade
Hackolade
Prometheus
Prometheus
Kubernetes
Kubernetes
Datadog
Datadog
Kafka
Kafka
Apache Spark
Apache Spark

What are some alternatives to InfluxDB, ScyllaDB?

MongoDB

MongoDB

MongoDB stores data in JSON-like documents that can vary in structure, offering a dynamic, flexible schema. MongoDB was also designed for high availability and scalability, with built-in replication and auto-sharding.

MySQL

MySQL

The MySQL software delivers a very fast, multi-threaded, multi-user, and robust SQL (Structured Query Language) database server. MySQL Server is intended for mission-critical, heavy-load production systems as well as for embedding into mass-deployed software.

PostgreSQL

PostgreSQL

PostgreSQL is an advanced object-relational database management system that supports an extended subset of the SQL standard, including transactions, foreign keys, subqueries, triggers, user-defined types and functions.

Microsoft SQL Server

Microsoft SQL Server

Microsoft® SQL Server is a database management and analysis system for e-commerce, line-of-business, and data warehousing solutions.

SQLite

SQLite

SQLite is an embedded SQL database engine. Unlike most other SQL databases, SQLite does not have a separate server process. SQLite reads and writes directly to ordinary disk files. A complete SQL database with multiple tables, indices, triggers, and views, is contained in a single disk file.

Cassandra

Cassandra

Partitioning means that Cassandra can distribute your data across multiple machines in an application-transparent matter. Cassandra will automatically repartition as machines are added and removed from the cluster. Row store means that like relational databases, Cassandra organizes data by rows and columns. The Cassandra Query Language (CQL) is a close relative of SQL.

Memcached

Memcached

Memcached is an in-memory key-value store for small chunks of arbitrary data (strings, objects) from results of database calls, API calls, or page rendering.

MariaDB

MariaDB

Started by core members of the original MySQL team, MariaDB actively works with outside developers to deliver the most featureful, stable, and sanely licensed open SQL server in the industry. MariaDB is designed as a drop-in replacement of MySQL(R) with more features, new storage engines, fewer bugs, and better performance.

RethinkDB

RethinkDB

RethinkDB is built to store JSON documents, and scale to multiple machines with very little effort. It has a pleasant query language that supports really useful queries like table joins and group by, and is easy to setup and learn.

ArangoDB

ArangoDB

A distributed free and open-source database with a flexible data model for documents, graphs, and key-values. Build high performance applications using a convenient SQL-like query language or JavaScript extensions.

Related Comparisons

Bootstrap
Materialize

Bootstrap vs Materialize

Laravel
Django

Django vs Laravel vs Node.js

Bootstrap
Foundation

Bootstrap vs Foundation vs Material UI

Node.js
Spring Boot

Node.js vs Spring-Boot

Liquibase
Flyway

Flyway vs Liquibase