throttle-io-stream
stm-containers
| throttle-io-stream | stm-containers | |
|---|---|---|
| - | 2 | |
| 5 | 62 | |
| - | - | |
| 0.0 | 3.7 | |
| about 1 year ago | 10 days ago | |
| Haskell | Haskell | |
| BSD 3-clause "New" or "Revised" License | MIT 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.
throttle-io-stream
We haven't tracked posts mentioning throttle-io-stream yet.
Tracking mentions began in Dec 2020.
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?
What are some alternatives?
stm-conduit - STM-based channels for conduits.
stm-incremental - A very simple interface for incremental computation using STM in Haskell.
async - Run IO operations asynchronously and wait for their results
restricted-workers - Interactive-diagrams
pipes-concurrency - Concurrency for the pipes ecosystem
stm-chunked-queues - Thread communication queues that group items/requests that occur close together in time
consumers
theatre - Minimalistic actor library for Haskell
mvc-updates - Concurrent and combinable updates
named-lock - A named lock that is created on demand.
cspmchecker - The library FDR3 uses for parsing, type checking and evaluating machine CSP.
conceit - Concurrently + Either