At a crossroads

• hackage-server

  19 407 8.3 Haskell

  Hackage-Server: A Haskell Package Repository

  

Questions re. library support are best found by searching Hackage. A cursory glance indicates ‘yes’ to both, though I’ve never used them. Generally, there is a library to do what you want, though given the Haskell community’s relatively small size and finite time, it might not be as up-to-date as you like. That, of course, is a problem that you can fix and contribute upstream, and the Haskell build tools have good support for using your own fork of a given library.

• graphql-client

  2 25 6.8 TypeScript

  Call and consume GraphQL APIs with type safe queries and responses (by brandonchinn178)

  

- Branitree seems to expose GraphQL API. You should be able to access it with one of Haskell GraphQL client libraries, either morpheus-graphql-client ( https://hackage.haskell.org/package/morpheus-graphql-client ) or graphql-client ( https://hackage.haskell.org/package/graphql-client )

• InfluxDB

  www.influxdata.com featured

  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.

  

• icicle

  2 18 6.7 Haskell

  Icicle Streaming Query Language (by icicle-lang)

  

We used Haskell as a general purpose programming language, so any tool that needed writing we wrote in Haskell (almost). That included AWS infrastructure using Amazonka, cli programs for running data analysis, websites with servant and purescript, new libraries to interact with services like Github and Azure, compilers https://github.com/icicle-lang/icicle. As a general purpose language it is great! The places where we couldn't and didn't use Haskell was either due to needing the JVM or specific JVM integrations like Kafka or Hadoop. Or because the code was written by non-Engineers for things like prototypes or generating reports (usually Python or R) The trouble you run into with Haskell (or any other less popular) language is missing libraries, you need to commit to writing them yourself or changing languages that include them. At one point we needed integration with Azure and MSSQL, and ended up using F# so we had access to .NET. For other Azure services we wrote REST clients to call the endpoints we needed.

• post-rfc

  27 2,185 2.3

  Blog post previews in need of peer review

At work, we tend to build so-called "serverless" APIs, running on AWS. Haskell's story for maintainable software, provided you have the libraries, is excellent. The State of the Haskell Ecosystem document is a good starting point. Once you have a toe-hold running systems in production, the cost of building "just that one missing library" is often not too bad.

Suggest a related project