Datahike VS EdgeDB

• Persistence
  Datahike is a persistent database, which means that it retains data across sessions and can be relied upon for storage that survives application restarts.
• Datalog queries
  Datahike supports Datalog queries, a powerful and expressive query language that is similar to Prolog, allowing for complex querying of data relationships.
• Schema flexibility
  Datahike provides schema flexibility that allows developers to define and evolve their data models without needing to perform migrations. This can significantly speed up development.
• Immutable data structures
  By utilizing immutable data structures, Datahike allows safe concurrent reads and writes, reducing the risk of data corruption and improving application stability.
• Transactional support
  Datahike offers ACID-compliant transactions, ensuring data integrity and consistent state even in the face of concurrent operations.
• Integration with Datomic API
  Datahike is designed to be compatible with the Datomic API, making it easier for developers familiar with Datomic to transition and leverage their knowledge.
• Off-the-shelf scalability
  The architecture of Datahike is conducive to scaling horizontally, providing flexibility to handle growing amounts of data and user load.

Possible disadvantages

• Relatively new ecosystem
  Being a lesser-known and newer alternative compared to databases like Datomic, Datahike may have a smaller community and fewer resources like documentation and third-party integrations.
• Performance limitations
  While Datahike is designed to be lightweight and flexible, it may not match the performance of more mature databases, especially in very high-load or high-volume scenarios.
• Limited features
  Datahike may lack some advanced features present in other databases, such as sophisticated indexing or native support for certain types of analytics, which could be necessary for specific applications.
• Java Virtual Machine (JVM) requirement
  As it runs on the JVM, Datahike requires a Java runtime environment, which might not be ideal or convenient for projects seeking to minimize dependencies or employ lightweight deployment strategies.

• Graph-Relational Model
  EdgeDB combines the features of relational and graph databases, allowing for complex queries and relationships while maintaining data integrity typical in relational databases.
• Advanced Query Language (EdgeQL)
  EdgeQL offers a more intuitive and expressive query syntax compared to traditional SQL, facilitating easier and more efficient data retrieval.
• Schema Evolution
  EdgeDB provides robust tools for schema migrations and versioning, making it easier to evolve the database schema without downtime or data loss.
• Type Safety
  With its strong typing system, EdgeDB reduces runtime errors by ensuring data type consistency across the database operations.
• Integrated Indexing and Constraints
  EdgeDB supports advanced indexing and constraints, improving query performance and maintaining data integrity natively.

Possible disadvantages

• Relative Newness
  Being relatively new in the market, EdgeDB might lack extensive community support and third-party integrations compared to more established databases.
• Learning Curve
  Technicians accustomed to traditional SQL or other database paradigms might face a learning curve when adapting to EdgeDB's unique features and query language.
• Limited Ecosystem
  EdgeDB's ecosystem, including tooling, documentation, and community resources, is less mature compared to other well-established database systems.
• Potential for Rapid Changes
  As a developing technology, EdgeDB may undergo rapid changes and updates, which may lead to instability or additional maintenance overhead.
• Hosting and Compatibility Concerns
  Deploying EdgeDB might have specific hosting requirements, and compatibility with existing infrastructure could be a concern for some users.

No Datahike videos yet. You could help us improve this page by suggesting one.

Checking out EdgeDB - The Developer Database (Better than Prisma ORM?!)

More videos

• What if database branching was easy?

  It appears that Datahike [0] is a Datomic workalike that supports branching. I haven’t tried it out myself (yet), but the documentation suggests it’s possible [1]. That said, I’m adding xitdb to the list of tech to try out. Thank you for... - Source: Hacker News / 6 months ago

• Show HN: Stratum – SQL that branches and beats DuckDB on 35/46 1T benchmarks

  Hey. Hybrid in which sense? I have integrated Stratum's columnar indices as a secondary index in the new query engine of https://github.com/replikativ/datahike itself, so for numerical data you will be able to use Datalog/SQL to have... - Source: Hacker News / 7 months ago

• The Ten Rules of Schema Growth

  Datahike [0] provides similar functionality to datomic and is open source. It lacks some features however that Datomic does have [1]. [0]: https://github.com/replikativ/datahike. - Source: Hacker News / almost 3 years ago

View more

• Beyond SQL: A relational database for modern applications

  A new DB, with a new query language that's like "SQL done right"? This immediately reminded me of EdgeDB: https://edgedb.com/ Is there anyone here who knows enough about these two products to do a compare/contrast? - Source: Hacker News / about 3 years ago

• Beyond SQL: A relational database for modern applications

  See also https://edgedb.com/ which is another relational database without sql. - Source: Hacker News / about 3 years ago

• DuckDB 0.8.0

  >relational no-sql Do you mean something like edgeDB?[0] Or do you mean some non-declarative language completely? I don't see the latter making much sense. The issue with SQL for me is the "natural language" which quickly loses all... - Source: Hacker News / over 3 years ago

View more