orcaman/concurrent-map
a thread-safe concurrent map for go observed · 2026-08-28
Health v2 · maintenance only
23/100
- Activity 0
- Release rhythm 8
- Longevity 100
How is this computed?
round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10) — computed 2026-09-02. Adoption (stars, forks) is never an input.
- gap_med: n/a
- age_days: 4350
- days_rel: n/a
- days_push: 833
- n_releases_24m: 0
Adoption not part of the score
4530 stars · 554 forks observed · 2026-08-28
What it is AI-extracted, prompt v1, taxonomy v1, 2026-08-29, confidence not recorded
A thread-safe concurrent map implementation for Go that shards the map to minimize lock contention. It predates and complements the stdlib sync.Map, which is optimized for append-only scenarios.
Use cases
- share a map between goroutines safely
- use a map as a simple in-memory database
- avoid manual mutex locking around Go maps
- high-throughput concurrent key-value access
- replace sync.Map for mixed read/write workloads
When to choose
- you need concurrent reads and writes to a shared map with frequent updates
- sync.Map's append-only design doesn't fit your access pattern
- you want a map API close to the native Go map
When to avoid
- your workload is append-only or read-mostly, where sync.Map is faster
- you're on Go 1.9+ and stdlib sync.Map suffices
- you need persistence or a full in-memory database
Facets
library · maturity stable
concurrency caching developer-tools performance go cross-platform thread-safe sharded-map concurrent-map in-memory-store algorithms
1 source
- readme: https://github.com/orcaman/concurrent-map · fetched 2026-08-28 · b360cdc9f18a
Member repositories
| Repository | Role | Health v2 |
|---|---|---|
| orcaman/concurrent-map | main | 23 |
For agents
markdown · JSON · MCP: product_card(name="orcaman/concurrent-map")
Data as of 2026-08-30T08:39:29.467469+00:00 · Report a problem