DEV.co
Open-Source Databases · strapdata

elassandra

Elassandra merges Apache Cassandra (a distributed NoSQL database) with Elasticsearch (a search engine) into a single system. It enables full-text search, real-time aggregations, and cross-datacenter replication on Cassandra data without needing separate infrastructure.

Source: GitHub — github.com/strapdata/elassandra
1.7k
GitHub stars
194
Forks
Java
Primary language
Apache-2.0
License (OSI-approved)

Key facts

Objective fields from the source. Values we can't verify are shown as “Unknown” rather than guessed.

FieldValue
Repositorystrapdata/elassandra
Ownerstrapdata
Primary languageJava
LicenseApache-2.0 — OSI-approved
Stars1.7k
Forks194
Open issues60
Latest releasev6.2.3.38 (2022-03-28)
Last updated2026-05-17
Sourcehttps://github.com/strapdata/elassandra

What elassandra is

Elassandra embeds Elasticsearch within Cassandra nodes, using Cassandra as the primary data and configuration store while Elasticsearch indexes provide search capabilities. It supports multi-master replication, horizontal scaling via vnodes, and REST/CQL access patterns, eliminating the need for a separate search cluster.

Quickstart

Get the elassandra source

Clone the repository and explore it locally.

terminalbash
git clone https://github.com/strapdata/elassandra.gitcd elassandra# follow the project's README for install & configuration

Need it deployed, integrated, or customized instead? DEV.co ships production installs.

Best use cases

Multi-datacenter deployments with active/active replication

Organizations needing cross-datacenter search and write availability benefit from Elassandra's masterless architecture and Cassandra's built-in replication. No single point of write failure; write to nearest datacenter and search globally.

Unified data + search storage to reduce operational overhead

Teams running both Cassandra and Elasticsearch can consolidate into one system, reducing infrastructure complexity, security surface, and disk space. Source documents remain in Cassandra, avoiding duplication.

Real-time full-text search on high-volume, time-series data

Systems requiring low-latency search with aggregations on Cassandra tables (e.g., logs, metrics) avoid Spark/Hadoop batch processing. Indexing happens automatically on writes.

Implementation considerations

  • Cassandra replication factor for elastic_admin keyspace must be managed manually (minimum 3 per datacenter for PAXOS quorum); not auto-adjusted in 6.2.3.21+.
  • Rolling upgrades require careful coordination: avoid Elasticsearch mapping changes during upgrades to prevent inconsistency between old and new versions.
  • X1 gossip compression (-Des.compress_x1=true) should be enabled post-upgrade to 6.8.4.2+ for large numbers of indices; requires cluster-wide restart.
  • CQL schema extensions (v6.2.3.8+) store Elasticsearch mappings in binary format; older cqlsh tools may fail; use bundled cqlsh or pip-installed version.
  • Horizontal scaling adds search throughput (unlike standard Elasticsearch which requires shard redistribution); but operational complexity of multi-node Cassandra must be managed.

When to avoid it — and what to weigh

  • Elasticsearch-only search use cases — If you only need Elasticsearch and not a persistent, replicated NoSQL store, standard Elasticsearch is simpler and better supported by Elastic.
  • Need for latest Elasticsearch versions and rapid feature updates — Latest release is v6.2.3.38 from March 2022. Elasticsearch is now at v8+. Elassandra trails significantly in version and may not include recent security patches or features from Elastic.
  • Small-scale, simple search-only projects — Operational complexity of a distributed system is unnecessary if you need basic search on modest data volumes. Standard search engines or managed services are faster to deploy.
  • Strict commercial support requirements — Project is community-driven with no clear commercial support organization stated. If you require guaranteed SLAs and vendor backing, assess alternatives.

License & commercial use

Elassandra is licensed under Apache License 2.0, a permissive OSI-approved license allowing commercial use, modification, and distribution with minimal restrictions.

Apache 2.0 permits commercial use without explicit license fees or restrictions. However, no commercial support organization is identified in the provided data. Organizations requiring SLAs, professional support, or guaranteed maintenance should verify support arrangements directly with Strapdata or the community.

DEV.co evaluation signals

Editorial assessment — not user reviews. Directional, with an explicit confidence level.

SignalAssessment
MaintenanceModerate
DocumentationAdequate
License clarityClear
Deployment complexityHigh
DEV.co fitPossible
Assessment confidenceMedium
Security considerations

No explicit security audit, vulnerability disclosure policy, or hardening guidance provided in available data. Apache 2.0 license and Java implementation mean standard Java/Cassandra/Elasticsearch security practices apply. Evaluate: network segmentation, authentication/authorization plugins, encryption at rest/transit, compliance with your threat model. Verify current patch status for embedded Elasticsearch (v6.x) against known CVEs.

Alternatives to consider

Elasticsearch + separate Cassandra

Maintains flexibility to upgrade Elasticsearch independently, use latest versions, and leverage Elastic's commercial support. Adds operational overhead but reduces lock-in and version lag.

OpenSearch (AWS-maintained Elasticsearch fork) + Cassandra

OpenSearch is more actively maintained than Elasticsearch 6.x and includes security plugins out-of-box. Similar dual-system trade-offs as plain Elasticsearch.

Cloud-managed search services (e.g., Elasticsearch Cloud, OpenSearch Serverless)

Eliminates deployment and operational complexity for search; pairs with self-managed Cassandra or cloud Cassandra services if unified storage is not required.

Software development agency

Build on elassandra with DEV.co software developers

Assess your multi-datacenter search and replication requirements. Verify commercial support availability and test version compatibility with your Elasticsearch tooling. Consult a database architect familiar with both Cassandra and Elasticsearch.

Talk to DEV.co

Related open-source tools

Surfaced by semantic similarity across the DEV.co open-source index.

Related on DEV.co

Explore the category and the services that help you build with it.

elassandra FAQ

Can I upgrade Elassandra independently of Elasticsearch?
No. Elassandra versions are tied to embedded Elasticsearch versions (e.g., 6.2.3.x). Upgrading Elassandra requires operational overhead and mapping-change restrictions during rolling restarts.
Is Elassandra suitable for production with SLA requirements?
Requires careful evaluation. No official commercial support organization is identified. Production use demands in-house Cassandra/Elasticsearch expertise, thorough testing, and potentially commercial support from Strapdata (if available) or a third party.
What is the version lag compared to standard Elasticsearch?
Latest Elassandra release (v6.2.3.38, March 2022) embeds Elasticsearch 6.x. Current Elasticsearch is v8+. This gap means missing 2+ years of features, security patches, and performance improvements.
Can I run Elassandra in Kubernetes?
A Google Kubernetes Engine tutorial exists, but no dedicated Helm charts or operator are documented. Deployment-as-code tooling maturity is unknown; requires custom orchestration or third-party tooling.

Software development & web development with DEV.co

Adopting elassandra is usually one piece of a larger software development effort. As a software development agency, DEV.co provides software development services and web development expertise — pairing senior software developers and web developers with your team to design, build, and operate open-source databases software in production.

Ready to evaluate Elassandra?

Assess your multi-datacenter search and replication requirements. Verify commercial support availability and test version compatibility with your Elasticsearch tooling. Consult a database architect familiar with both Cassandra and Elasticsearch.