Open-Awesome
CategoriesAlternativesStacksSelf-HostedExplore
Open-Awesome

© 2026 Open-Awesome. Curated for the developer elite.

TermsPrivacyAboutGitHubRSS
  1. Home
  2. Go
  3. eliasdb

eliasdb

MPL-2.0Gov1.4.0

EliasDB is a lightweight graph-based database with GraphQL support, a custom query language, and built-in scripting.

GitHubGitHub
1.0k stars48 forks0 contributors

What is eliasdb?

EliasDB is a lightweight, graph-based database written in Go that stores data as interconnected nodes and edges. It provides built-in search, querying, and scripting capabilities, designed for projects requiring flexible graph data structures with minimal external dependencies. It can be embedded in Go applications or run as a standalone application with an HTTPS webserver.

Target Audience

Go developers building applications that need an embedded or standalone graph database with transactional support, full-text search, and GraphQL/EQL querying. It's also suitable for projects requiring extensibility through scripting for backend logic or database operation actions.

Value Proposition

Developers choose EliasDB for its self-contained design with no external dependencies (except gorilla/websocket for GraphQL subscriptions), offering both an embeddable library and a standalone server. Its unique combination of a custom key-value store, GraphQL interface, EQL query language, and ECAL scripting interpreter provides a versatile, all-in-one solution for graph data management.

Overview

EliasDB a graph-based database.

Use Cases

Best For

  • Embedding a transactional graph database within Go applications that require rule-based consistency management and data iteration.
  • Building standalone applications that need a graph database with a built-in HTTPS webserver, REST API, and user management for web interfaces.
  • Implementing projects requiring complex graph queries using both a custom SQL-like EQL language and a GraphQL interface for flexible data retrieval.
  • Developing applications that need full-text search capabilities across all stored graph data for fast phrase lookups.
  • Creating extensible backend systems where database operations (store, update, delete) require custom logic defined via the ECAL scripting interpreter.
  • Running clustered database instances for distributed data storage and management, as EliasDB supports multiple instances in a cluster.

Not Ideal For

  • Enterprises requiring robust, production-ready distributed clustering, as support is experimental and not fully stable.
  • Teams standardized on graph query languages like Cypher or Gremlin, due to reliance on the proprietary EQL syntax.
  • Projects needing extensive third-party integrations or ORM support across multiple programming languages, given its Go-centric design.
  • Applications with massive datasets requiring horizontal scaling beyond lightweight, embedded solutions.

Pros & Cons

Pros

Self-Contained Architecture

Built with minimal external dependencies—only gorilla/websocket for GraphQL subscriptions—making deployment straightforward and reducing maintenance overhead.

Dual Query Interface

Offers both a GraphQL interface for flexible data retrieval and a custom EQL language for complex SQL-like queries, providing versatile querying options as highlighted in the features.

Embedded and Standalone Versatility

Can be embedded in Go applications with transactional support or run as a standalone app with a built-in HTTPS server, REST API, and user management, detailed in the getting started sections.

Extensible Scripting Engine

Includes the ECAL scripting interpreter for defining custom actions on database operations, enabling backend logic integration without external tools, as described in the scripting section.

Cons

Experimental Clustering

Clustering support is marked as EXPERIMENTAL in the configuration options, indicating it's not yet stable for production use in distributed environments.

Proprietary Query Language

Relies on its own EQL query language, which requires learning a new syntax instead of leveraging industry standards like Cypher, potentially increasing the learning curve.

Go-Centric Limitations

Primarily designed for Go applications; embedding is limited to Go, and there's no mention of native drivers for other languages, restricting cross-platform adoption.

Frequently Asked Questions

Quick Stats

Stars1,035
Forks48
Contributors0
Open Issues13
Last commit14 days ago
CreatedSince 2016

Tags

#database#graph#graphql#embedded#query-language#rest-api#swagger#standalone#key-value-store#embedded-database#scripting#golang#full-text-search#eql#graph-database#transactional#go#self-hosted#tutorial

Built With

G
Go
G
Gorilla WebSocket

Included in

Go169.1k
Auto-fetched 9 hours ago

Related Projects

Prometheus.ioPrometheus.io

The Prometheus monitoring system and time series database.

Stars66,003
Forks10,830
Last commit15 hours ago
MilvusMilvus

Milvus is a high-performance, cloud-native vector database built for scalable vector ANN search

Stars46,019
Forks4,238
Last commit9 hours ago
TiDBTiDB

TiDB is built for agentic workloads that grow unpredictably, with ACID guarantees and native support for transactions, analytics, and vector search. No data silos. No noisy neighbors. No infrastructure ceiling.

Stars40,499
Forks6,238
Last commit10 hours ago
cockroachcockroach

CockroachDB — the cloud native, distributed SQL database designed for high availability, effortless scale, and control over data placement.

Stars32,445
Forks4,104
Last commit5 days ago
Community-curated · Updated weekly · 100% open source

Found a gem we're missing?

Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.

Submit a projectStar on GitHub