stm-containers
named-lock
Our great sponsors
| stm-containers | named-lock | |
|---|---|---|
| 2 | - | |
| 62 | 1 | |
| - | - | |
| 5.6 | 0.0 | |
| 6 months ago | over 14 years ago | |
| Haskell | Haskell | |
| MIT License | BSD 3-clause "New" or "Revised" License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
stm-containers
-
Software Transactional Memory (1997)
I think you are right about STM being roughly equivalent to snapshot isolation.
What STM offers is an easy way to invent "containers for snapshotted values" aka TVars. Using them carefully may result in better scaling: https://hackage.haskell.org/package/stm-containers
-
How to achieve "Run at most one parallel async action per user"?
how about use stm-containers?
named-lock
We haven't tracked posts mentioning named-lock yet.
Tracking mentions began in Dec 2020.
What are some alternatives?
stm-incremental - A very simple interface for incremental computation using STM in Haskell.
concurrent-supply - A fast globally unique variable supply with a pure API
restricted-workers - Interactive-diagrams
stm-conduit - STM-based channels for conduits.
stm-chunked-queues - Thread communication queues that group items/requests that occur close together in time
timeout - Generalized sleep and timeout functions
theatre - Minimalistic actor library for Haskell
stm-queue-extras - Extra utilities for STM queues
conceit - Concurrently + Either
concurrent-machines - Concurrency features for the Haskell machines package
ttrie - A contention-free STM hash map for Haskell
BoundedChan - Bounded (limited capacity) channels for Haskell