cloud-haskell VS Workflow

Compare cloud-haskell vs Workflow and see what are their differences.

cloud-haskell

This is an umbrella development repository for Cloud Haskell (by haskell-distributed)

Workflow

re-startable monad that recover the execution state from a log, and workflow patterns (by agocorona)
Our great sponsors
  • InfluxDB - Power Real-Time Data Analytics at Scale
  • WorkOS - The modern identity platform for B2B SaaS
  • SaaSHub - Software Alternatives and Reviews
cloud-haskell Workflow
- 1
72 42
- -
0.0 0.0
over 5 years ago almost 8 years ago
Haskell
BSD 3-clause "New" or "Revised" License BSD 3-clause "New" or "Revised" License
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
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.

cloud-haskell

Posts with mentions or reviews of cloud-haskell. We have used some of these posts to build our list of alternatives and similar projects.

We haven't tracked posts mentioning cloud-haskell yet.
Tracking mentions began in Dec 2020.

Workflow

Posts with mentions or reviews of Workflow. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2021-08-11.
  • Event Sourcing
    8 projects | news.ycombinator.com | 11 Aug 2021
    I was part of that debate, I remember a rather interesting point of discussion: Is the main operation "apply" or "dedup"

    Apply seems to be the common notion of event sourcing: There is a function apply that takes a state an event and yields a new state. Then, starting in an init state and iteratively applying the entire event history, boom, latest state restored.

    Dedup has a lot of charm though: Run and rerun your code, if that step of your code is executed for the first time (no corresponding event in the event history) execute the step and store its result as an event in the history, however, if that step of your code is executed for the second, third time (there is a corresponding event in the event history) do not execute the step and return its result from the event in the history. The Haskell Workflow Package (https://hackage.haskell.org/package/Workflow) is a good example

    Temporal follows the second approach, so "proper" Event Sourcing? You be the judge :)

What are some alternatives?

When comparing cloud-haskell and Workflow you can also consider the following projects:

unpack-funcs - Unpacking reader monad transformers in Haskell

unliftio - The MonadUnliftIO typeclass for unlifting monads to IO

lens-tutorial - The missing tutorial module for the lens library

effect-monad - Provides 'graded monads' and 'parameterised monads' to Haskell, enabling fine-grained reasoning about effects.

basic-prelude - An enhanced core prelude, meant for building up more complete preludes on top of.

record - Anonymous records

abstract-par

recursion-schemes - Generalized bananas, lenses and barbed wire

rio-orphans - A standard library for Haskell

hask - Category theory for Haskell with a lens flavor (you need GHC 7.8.3, not 7.8.2 to build this!)

monad-time