OpenHFT/Chronicle-Map
View on GitHub ↗ ★ 2,995 Java
Replicate your Key Value Store across your network, with consistency, persistance and performance.
8 mentions on Hacker News by 8 people: 5 stories, 3 comments · first 2014-10-17 · latest 2023-09-16
20082026
-
…IPC. IPC isn't limited to network calls, it can be as simple as shared memory and hit millions of OPS: github.com/OpenHFT/Chronicle-Map > I'm not convinced; if my small/specific code has its own process, I would say it's a microservice.…
comment by BoorishBears · 2023-09-16 · in How Instagram scaled to 14 million users with only 3 engineers -
…on top of a NVME drive that was IOMMU passthrough'd to this VM for maximum performance. As well as https://github.com/OpenHFT/Chronicle-Map , which really helped out. We needed a mapping from block coordinate to a bit of data about that…
comment by leijurv · 2021-12-19 · in Nocom – 2b2t Minecraft server exploit using Monte-Carlo localization -
▲ 1
Chronicle Map: Replicate your Key Value Store across your networkstory by script3r · 2020-07-06 · 0 comments
-
▲ 2
Chronicle Map: Distributed, Multi-master, Mutli-process, KV store for the JVMstory by ignoramous · 2018-01-17 · 0 comments
-
very cool! any idea how this would compare to clojure-wrapping https://github.com/OpenHFT/Chronicle-Map ? Seems like there are some similar design goals between the two.
comment by tuddman · 2016-08-05 · in Hitchhiker trees: functional, persistent, off-heap sorted maps -
▲ 1
Production release of Chronicle Map 3story by javinpaul · 2016-03-25 · 0 comments
-
▲ 1
Chronicle Map 3: in-memory key-value store for low-latency Javastory by leventov · 2016-03-23 · 0 comments
-
▲ 2
Chronicle: Replicate your Key Value Store across your networkstory by bra-ket · 2014-10-17 · 0 comments