stm-conduit
stm-containers
Our great sponsors
| stm-conduit | stm-containers | |
|---|---|---|
| - | 2 | |
| 41 | 62 | |
| - | - | |
| 3.8 | 5.6 | |
| 9 months ago | 6 months 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.
stm-conduit
We haven't tracked posts mentioning stm-conduit 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?
streamly - High performance, concurrent functional programming abstractions
stm-incremental - A very simple interface for incremental computation using STM in Haskell.
restricted-workers - Interactive-diagrams
stm-channelize - Transactional I/O for duplex streams
stm-chunked-queues - Thread communication queues that group items/requests that occur close together in time
throttle-io-stream - Throttler between a producer and a consumer function
theatre - Minimalistic actor library for Haskell
named-lock - A named lock that is created on demand.
stm-queue-extras - Extra utilities for STM queues
conceit - Concurrently + Either