Datomic VS Apache Ignite

• Immutability
  Datomic employs an append-only data model where data is never overwritten but instead appended, ensuring historical data is always available and providing strong consistency.
• Time Travel Queries
  Datomic allows you to query the database as of any point in time, facilitating auditing and debugging by allowing easy access to historical data states.
• Rich Data Model
  Supports complex data types like maps and sets directly within its schema, providing a flexible way to represent data.
• ACID Transactions
  Datomic supports fully ACID-compliant transactions, ensuring reliable and predictable database operations.
• Scalability
  Separates storage and compute, allowing for horizontal scaling of read operations, making it suitable for handling large datasets.
• Query Flexibility
  Offers a powerful query language that supports recursive queries, making it suitable for complex data retrieval needs.

Possible disadvantages

• Complexity
  The architecture of Datomic can be complex to understand and implement, particularly for teams unfamiliar with its design principles.
• Cost
  Can be expensive to operate, especially in a cloud environment, where costs increase with the amount of data stored and the compute resources required.
• Limited Write Throughput
  Due to its append-only design, Datomic can have limited write throughput, which may not be suitable for applications with heavy write requirements.
• Closed Source
  Datomic is a proprietary database system, which may not appeal to organizations that prefer open-source solutions.
• Learning Curve
  Requires a learning curve as its conceptual model and query language are different from traditional databases, potentially requiring additional training.
• Dependency on AWS
  Relying on AWS ecosystem for the storage backend can limit choices for deployment environments, impacting flexibility.

• In-Memory Data Grid
  Apache Ignite provides a robust in-memory data grid that can drastically improve data access speeds by storing data in memory across distributed nodes.
• Scalability
  The system is designed to scale horizontally, allowing users to add more nodes to handle increased loads, thereby ensuring high availability and performance.
• Distributed Compute Capabilities
  Ignite supports parallel execution of tasks across cluster nodes, which is beneficial for complex computations and real-time processing.
• Persistence
  Although primarily in-memory, Ignite offers a durable and transactional Persistence layer that ensures data can be persisted on disk, providing a hybrid in-memory and persistent storage solution.
• SQL Queries
  Ignite offers support for ANSI-99 SQL, which allows users to execute complex SQL queries across distributed datasets easily.
• Integration
  It integrates well with existing Hadoop and Spark setups, allowing users to enhance their existing data pipelines with Ignite’s capabilities.
• Fault Tolerance
  Apache Ignite includes built-in mechanisms for recovery and ensures that data copies are maintained across nodes for resilience against node failures.

Possible disadvantages

• Complexity
  Apache Ignite can be complex to set up and manage, especially when configuring a large, distributed system with multiple nodes.
• Resource Intensive
  Running an in-memory data grid like Ignite requires significant memory resources, which can increase operational costs.
• Learning Curve
  Due to its comprehensive features and distributed nature, there is a steep learning curve associated with effectively utilizing Ignite.
• Configuration Overhead
  There is substantial configuration overhead involved to optimize performance and ensure proper cluster management.
• Community Support
  Although it has active development, the community support might not be as robust compared to other more mature solutions, possibly leading to challenges in finding solutions to niche issues.
• YARN Dependence
  For those looking to integrate with Hadoop, Ignite's optimal performance is sometimes reliant on Hadoop YARN, which can introduce additional complexity.

KotlinConf 2018 - Datomic: The Most Innovative DB You've Never Heard Of by August Lilleaas

More videos

Best Practices for a Microservices Architecture on Apache Ignite

More videos

Tracking Datomic since Mar 2021.

• Rate Limiting in Spring Boot REST APIs: Bucket4j + Redis

  Yes, you can use rate limiting with other caching solutions, such as Apache Ignite. However, Redis is a popular choice for rate limiting due to its ease of use and flexibility. - Source: dev.to / 4 months ago

• API Caching: Techniques for Better Performance

  Apache Ignite — Free and open-source, Apache Ignite is a horizontally scalable key-value cache store system with a robust multi-model database that powers APIs to compute distributed data. Ignite provides a security system that can... - Source: dev.to / almost 2 years ago

• Ask HN: P2P Databases?

  Ignite works as you describe: https://ignite.apache.org/ I wouldn't really recommend this approach, I would think more in terms of subscriptions and topics and less of a 'database'. - Source: Hacker News / over 4 years ago

View more