Capataz

Our greatest glory is not in never failing, but in rising every time we fail.– Confucius

Table Of Contents

• Raison d'etre
• Documentation
• Development

Raison d'etre

As time progresses, I've come to love developing concurrent applications in Haskell, its API (STM, MVars, etc.) and light threading RTS bring a lot to the table. There is another technology that is more famous than Haskell in regards to concurrency, and that is Erlang, more specifically its OTP library.

If you wonder why that is, you may need to look into the OTP library design, actors systems (in general) provide an architecture that enables applications to be tolerant to failure through the enforcement of communication via message passing and by making use of a critical infrastructure piece called a Supervisor.

After trying to replicate Erlang's behavior on Haskell applications by using the distributed-process library (a clone of OTP), and after implementing several (disposable) iterations of actor systems in Haskell, I've settled with just this library, one that provides a simple Supervisor API.

This library is intended to be a drop-in replacement to forkIO invocations throughout your codebase, the difference being, you'll need to do a bit more of setup specifying supervision rules, and also pass along a reference of a capataz descriptor to every thread fork.

Why not distributed-process?

distributed-process is an impressive library, and brings many great utilities if you need to develop applications that are reliable. However, it is a heavyweight solution that will enforce serious changes to your application. It also optimizes its implementation around the distributed part of its name. This library is intended to provide some benefits of distributed-process , without the baggage.

Why not a complete actor system?

Actor systems are very pervasive, they impose specific design constraints on your application which can be rather expensive. This library attempts to bring some of the reliability benefits of actor systems without the "change all your application to work with actors" part of the equation.

That said, this library can serve as a basis for a more prominent library that provides an opinionated Inter-Process communication scheme. If you happen to attempt at doing exactly that, please let me know, I would love to learn about such initiatives.

Why not async?

async is a fabulous library that allows Applicative composition of small asynchronous sub-routines into bigger ones and link errors between them. Given this, async fits the bill perfectly for small operations that happen concurrently, not necessarily for long living threads that need to be restarted. This library attempts not to replace async's forte, but rather provides other benefits not found in async, like automatically restarting threads with a given recipe under error situations.

Documentation

Documentation can be found here

Installation

Make sure you include the following entry on your cabal file's dependecies section.

library:
  build-depends: capataz

Or on your package.yaml

dependencies:
- capataz

Development

Follow the developer guidelines

In next release

• Add support for supervising supervisors
• Ensure unit tests always finish on all concurrent scenarios (dejafu experiment)