Hazelcast vs. Citus



Hacker News, Reddit, Stack Overflow Stats

  • -
  • 16
  • 1.87K
  • 3.65K
  • 2.87K
  • 40

GitHub Stats

Description

What is Hazelcast?

With its various distributed data structures, distributed caching capabilities, elastic nature, memcache support, integration with Spring and Hibernate and more importantly with so many happy users, Hazelcast is feature-rich, enterprise-ready and developer-friendly in-memory data grid solution.

What is Citus?

Citus is worry-free Postgres for SaaS. Made to scale out, Citus is an extension to Postgres that distributes queries across any number of servers. Citus is available as open source, as on-prem software, and as a fully-managed service.

Want advice about which of these to choose?Ask the StackShare community!

Pros

Why do developers choose Hazelcast?
Why do you like Hazelcast?

Why do developers choose Citus?
Why do you like Citus?

Cons

What are the cons of using Hazelcast?
No Cons submitted yet for Hazelcast
Downsides of Hazelcast?

What are the cons of using Citus?
No Cons submitted yet for Citus
Downsides of Citus?

Pricing

How much does Hazelcast cost?
How much does Citus cost?
Citus Pricing

Companies

What companies use Hazelcast?
26 companies on StackShare use Hazelcast
What companies use Citus?
15 companies on StackShare use Citus

Integrations

What tools integrate with Hazelcast?
3 tools on StackShare integrate with Hazelcast
What tools integrate with Citus?
14 tools on StackShare integrate with Citus

What are some alternatives to Hazelcast and Citus?

  • Redis - An in-memory database that persists on disk
  • Aerospike - Flash-optimized in-memory open source NoSQL database
  • MemSQL - Database for real-time transactions and analytics.
  • LokiJS - In-memory JavaScript Datastore with Persistence

See all alternatives to Hazelcast

Latest News

Spring Integration Extension for Hazelcast 1.0.0 GA ...
Build a Spring Boot API with Hazelcast for Cached Us...
How the Citus distributed database rebalances your data
Citus 7.2: Distributed Postgres w/ CTEs, complex sub...
Citus and pg_partman: Creating a scalable time serie...