- attoparsec-conduit VS wai-conduit
- attoparsec-conduit VS shell-conduit
- attoparsec-conduit VS tar-conduit
- attoparsec-conduit VS conduit-audio
- attoparsec-conduit VS couchdb-conduit
- attoparsec-conduit VS shelf
- attoparsec-conduit VS binary-conduit
- attoparsec-conduit VS csv-conduit
- attoparsec-conduit VS conduit-combinators
- attoparsec-conduit VS http-conduit
Attoparsec-conduit Alternatives
Similar projects and alternatives to attoparsec-conduit
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
-
http-conduit
An HTTP client engine, intended as a base layer for more user-friendly packages. (by snoyberg)
attoparsec-conduit reviews and mentions
- Conduit question - what is "a single input value"?
-
Parallel streaming in Haskell: Part 1 – Fast, efficient, and fun
> makes me think that there aren't any conduits that have more data than can fit in memory on a single machine
Just because you can dedup a conduit doesn't mean you have to. We use conduits for streaming gigabytes-large files while staying within megabytes of memory use – ensuring that is one of the main selling points of libraries like conduit: https://github.com/snoyberg/conduit#readme
Stats
snoyberg/conduit is an open source project licensed under MIT License which is an OSI approved license.
The primary programming language of attoparsec-conduit is Haskell.