FS2 is a library for purely functional, effectful, and polymorphic stream processing library in the Scala programming language. Its design goals are compositionality, expressiveness, resource safety, and speed. The name is a modified acronym for Functional Streams for Scala (FSS, or FS2).
FS2 is available for Scala 2.12, Scala 2.13, Scala 3, and Scala.js.
FS2 is built upon two major functional libraries for Scala, Cats, and Cats-Effect.
Regardless of those dependencies, FS2 core types (streams and pulls) are polymorphic in the effect type (as long as it is compatible with cats-effect typeclasses),
and thus FS2 can be used with other effect libraries, such as Monix.
Prior to the 0.9 release in 2016, FS2 was known as scalaz-stream, which was based on the scalaz library.
Quick links:
- Microsite
- About the library
- How to get latest version
- API docs: fs2-core, fs2-io, fs2-reactive-streams, fs2-experimental
- Docs and getting help
- There are Scaladoc API documentations for the core library, which defines and implements the core types for streams and pulls, as well as the type aliases for pipes and sinks. The
iolibrary provides FS2 bindings for NIO-based file I/O and TCP/UDP networking. - The official guide is a good starting point for learning more about the library.
- The documentation page is intended to serve as a list of all references, including conference presentation recordings, academic papers, and blog posts, on the use and implementation of
fs2. - The FAQ has frequently asked questions. Feel free to open issues or PRs with additions to the FAQ!
- Also feel free to come discuss and ask/answer questions in the gitter channel and/or on StackOverflow using the tag FS2. Gitter will generally get you a quicker answer.
You can find a list of libraries and integrations with data stores built on top of FS2 here: https://fs2.io/#/ecosystem.
If you have a project you'd like to include in this list, either open a PR or let us know in the gitter channel and we'll add a link to it.
Special thanks to YourKit for supporting this project's ongoing performance tuning efforts with licenses to their excellent product.
See the Code of Conduct.