-
cromwell
Scientific workflow engine designed for simplicity & scalability. Trivially transition between one off use cases to massive scale production environments
-
-
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.
-
trading
💱 Trading application written in Scala 3 that showcases an Event-Driven Architecture (EDA) and Functional Programming (FP)
What about https://github.com/broadinstitute/cromwell ?
If you're using http4s, don't use ZIO. Yes, ZIO has an interop-cats module, so you can do this. But using http4s means you're working in the conceptual framework the Typelevel ecosystem is based on (and what interop-cats does can be characterized as "describe ZIO's implementation in those terms, so the Typelevel ecosystem can make heads or tails of it.") This is essentially all cost and no benefit: you can't avoid understanding the Typelevel ecosystem if you use http4s (at least, no more than you can by using cats-effect), and you don't get any of the value proposition of ZIO (interop-cats gives you Typelevel typeclass instances for the RIO type alias, which means your error channel is rooted in Throwable, and you're faced with the most complex part of the ZIO ecosystem: ZLayer, which the Typelevel ecosystem doesn't use and doesn't need). Finally the ZIO ecosystem is still quite immature, and this brings us to documentation. There is not (yet!) anything comparable to:
Functional Event-Driven Architecture for the ZIO ecosystem. I hear Zionomicon is evolving again, and that's good news. But there's literally years of more work to do.