Top all-time · #3011
Hazelcast
Company blog · hazelcast.com/blog · on HN as talipozturkdatasystems
Hazelcast is the company blog at hazelcast.com, writing about data and systems. Since 2010, 24 different Hacker News readers have linked it 41 times, most often “Hazelcast - an open source in-memory Java data grid”. It is still writing: the last post was on 2026-10-08, and you can follow it by feed.
Too few sampled comments (10) to say how often HN recommends it.?
Why HN links it
HN readers link Hazelcast's blog for its benchmarks of modern Java runtimes against JDK 8, and for posts on distributed locks, Jepsen testing of the CP subsystem, and distributed task coordination.
Summarised by Claude from a sample of 10 HN comments that link here. Each comment is marked recommending, critical or neutral (citing without judging); how this works.
Most-linked posts?
- Hazelcast - an open source in-memory Java data grid3 people · 3 mentions · first linked 2010-06-15
- In Fair Benchmark Hazelcast Beats Redis Says Greg Luck2 people · 2 mentions · first linked 2019-05-03
- Distributed Locks Are Dead; Long Live Distributed Locks2 people · 2 mentions · first linked 2019-04-03
- /blog/testing-the-cp-subsystem-with-jepsen/2 people · 2 mentions · first linked 2019-06-05
What Hacker News says?
Hazelcast | Fully Remote, European Time Zones | QA/Quality Lead | https://hazelcast.com/ I'm a Director of Engineering at Hazelcast. We build distributed systems at scale. We're looking for QA Leads/Engineers to help test our distributed storage and compute engines. If you want to do exciting work on distributed systems (think jepsen), find consistency and concurrency issues and do performance testing at scale, Haze…
Comment linking /
on “Ask HN: Who is hiring? (May 2020)”Submitted Distributed Locks Are Dead; Long Live Distributed Locks as a story · 110 points
HN discussion> That's debatable, and even if we blindly assume that then it's debatable whether the upgrade justifies the gains This is not debatable. It’s a factual truth. Every single actual performance review concludes that modern Java vastly out performs the decade old Java 8 runtime. For an example here is a quote from Hazelcast when comparing performance of modern Java on data heavy workloads [0]: > JDK 8 is an antiquated…
Comment linking /blog/performance-of-modern-java-on-data-heavy-workloads-part-1/
on “Java in the Small”Submitted Load Handling vs. Data Integrity: Tradeoffs in Distributed Data Store Design as a story · 36 points
HN discussionYou can't compare 10 years ago Java to current Go. 10 years ago was Java 8, we are currently on Java 23. The performance difference is massive between these 2 runtimes especially between the available garbage collectors. Hazelcast has a good blog [0] on their benchmarks between 8 and some of the more modern runtimes, here is one of their conclusions: > JDK 8 is an antiquated runtime. The default Parallel collector e…
Comment linking /blog/performance-of-modern-java-on-data-heavy-workloads-part-1/
on “Using Rust in non-Rust servers to improve performance”Submitted Announcing Hazelcast Jet 0.6 – The 3rd Generation Big Data Processing Engine as a story · 23 points
HN discussionLocations: Palo Alto, CA | New York Position: Senior Solutions Architect (fulltime) Company: Hazelcast, Inc. ( http://www.hazelcast.com ) Hazelcast is an in-memory data grid solution. As a Sn. Solutions Architect, you will work directly with customers and users to help them understand how they can use Hazelcast to achieve better performance and reliablity. Sn. Solutions Architect is an Hazelcast evangelist who loves…
Comment linking /
on “Ask HN: Who Is Hiring? (September 2012)”Submitted Tracing a single operation in distributed systems as a story · 13 points
HN discussionHow does this compare to Hazelcast[1]? Seems like the same idea, but far less features? [1] http://www.hazelcast.com/
Comment linking /
on “Groupcache: an alternative to memcached, written in Go”Submitted Redis Load Handling vs. Data Integrity: Tradeoffs in Distributed Store Design as a story · 9 points
HN discussionThey say they are using this: https://hazelcast.com/blog/idle-green-threads-in-jet/ And then say it's comparable. "This basic design is also present in the concepts of green threads and coroutines. In Hazelcast Jet we call them tasklets."
Comment linking /blog/idle-green-threads-in-jet/
on “Sub-10 ms Latency in Java: Concurrent GC with Green Threads”Submitted Whitepaper: Hazelcast for IBM for EXtremeScale Users as a story · 8 points
HN discussionThe truth is the original Hazelcast replication protocol was not a good fit for some data-structures. We took the analysis seriously. I know every project and vendor claims that. Here is what we did in recent years: 1. Re-implemented concurrency primitives on top of Raft protocol. This includes Distributed Locks, Semaphores, AtomicLong, etc. Raft provides linearizability and that's what you usually want for concurre…
Comment linking /blog/testing-the-cp-subsystem-with-jepsen/
on “Show HN: Jet – in-memory, fault-tolerant, distributed stream processing”Submitted Distributed Locks Are Dead; Long Live Distributed Locks as a story · 5 points
HN discussionThere was also a follow up blog post again by Basri regarding how it's tested using Jepsen for those interested: https://hazelcast.com/blog/testing-the-cp-subsystem-with-jep...
Comment linking /blog/testing-the-cp-subsystem-with-jepsen/
on “Distributed Locks Are Dead; Long Live Distributed Locks”Submitted Hazelcast and Kibana: best buddies for exploring and visualizing data as a story · 4 points
HN discussionThe new features make the code easier to read. For example var: List<Account> accounts = List.of(new Account(1), new Account(2)); var accounts = List.of(new Account(1), new Account(2)); It just reduces visual noise and boilerplate that you already know. Java 8 is also a slow and old runtime. It performs terribly in 2025. Here’s a quote from 2020 and the gap has only gotten wider [0]: > JDK 8 is an antiquated runtime…
Comment linking /blog/performance-of-modern-java-on-data-heavy-workloads-part-1/
on “All New Java Language Features Since Java 21”Submitted Where Is My Cache? Architectural Patterns for Caching Microservices as a story · 4 points
HN discussionOne of the popular existing job scheduler is Quartz, it is solid and does work pretty well up to a limit. The problem arises where we need to scale-out from a single master DB, there are some workarounds for that, but each has its limitations. ( https://hazelcast.com/blog/distributed-task-coordination-wit... ) While there are some existing solutions like BigBen from Walmart, it might be possible that they were overk…
Comment linking /blog/distributed-task-coordination-with-hazelcast/
on “Show HN: Clockwork- Distributed, Scalable Job Scheduler”Submitted Distributed locks are dead; long live distributed locks as a story · 4 points
HN discussionYou might get more responses if you posted in Stackoverflow. But here is what I wanted to share: You can keep the OS X as is. Load current JVM on all of them and connect them to a network. Then write a program that uses Hazelcast ( http://www.hazelcast.com/ ) that gives you a pseudo-distributed JVM cluster. It actually gives distributed Maps and Queues. Then mount a bunch of Jetlang ( http://code.google.com/p/jetlan…
Comment linking /
on “IMac Cluster?”Submitted ECommerce case study for in-memory caching at scale as a story · 4 points
HN discussionSubmitted Build Your Kubernetes Operator with the Right Tool as a story · 3 points
HN discussionSubmitted Quarkus Hazelcast Integration as a story · 3 points
HN discussionSubmitted An Experiment in Streaming: Bytecode Continuous Deployment as a story · 3 points
HN discussionSubmitted Hazelcast Jet 0.5 – New High-Level API Increases Developer Productivity as a story · 3 points
HN discussionSubmitted Speed up databases with Hazelcast (webinar) as a story · 3 points
HN discussionSubmitted LockSupport.parkNanos() Under the Hood and the Curious Case of Parking as a story · 2 points
HN discussionSubmitted Contract-First Development Using RestAssured and OpenAPI as a story · 2 points
HN discussionSubmitted Beyond “Hello World”: Zero-Downtime Deployments with Hazelcast on Kubernetes as a story · 2 points
HN discussion
