componentm: Monad for allocation and cleanup of application resources

[ library, mit, system ] [ Propose Tags ]

This library allows you to allocate resources with clean up strategies when initializing your application. It then provides a Monadic interface to compose multiple resources without having to deal with cleanup operations explicitely.


[Skip to Readme]

Downloads

Maintainer's Corner

Package maintainers

For package maintainers and hackage trustees

Candidates

  • No Candidates
Versions [RSS] 0.0.0.0, 0.0.0.1, 0.0.0.2
Change log CHANGELOG.md
Dependencies base (>=4.8 && <5), containers (>=0.5.7), deepseq (>=1.4.2), exceptions (>=0.8.3), pretty-show (>=1.6.13), prettyprinter (>=1.1), rio (>=0.0.3), teardown (>=0.3) [details]
License MIT
Copyright © 2017-current Roman Gonzalez
Author Roman Gonzalez
Maintainer open-source@roman-gonzalez.info
Category System
Home page https://github.com/roman/Haskell-componentm#readme
Bug tracker https://github.com/roman/Haskell-componentm/issues
Source repo head: git clone https://github.com/roman/Haskell-componentm
Uploaded by RomanGonzalez at 2018-05-20T21:44:43Z
Distributions LTSHaskell:0.0.0.2, NixOS:0.0.0.2, Stackage:0.0.0.2
Reverse Dependencies 1 direct, 1 indirect [details]
Downloads 2147 total (13 in the last 30 days)
Rating (no votes yet) [estimated by Bayesian average]
Your Rating
  • λ
  • λ
  • λ
Status Docs available [build log]
Last success reported on 2018-05-20 [all 1 reports]

Readme for componentm-0.0.0.2

[back to package description]

componentm

An utility library to build multiple components (config, db, cache, logging, etc.) of an application in a traceable, reliable and efficient fashion

Table Of Contents

Installation

Hackage Stackage LTS Stackage Nightly

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

library:
  build-depends: componentm

Or on your package.yaml

dependencies:
- componentm

Purpose

This library is intended to be a high level API for the teardown library; it provides a high level monad interface that helps composition of resource allocation/teardown in a safe and reliable way.

Differences with ResourceT

The resourcet library provides a monad transformer that keeps track of allocated resources at runtime making sure that if an exception happens or the block of execution finishes, the resources allocated are cleaned up.

The componentm library on the other hand, does not run as a Monad transformer, but rather it gets called at the very beginning of your application, it builds the environment needed by your application environment to work (e.g. Layer 1), and provides helper bracket style functions that cleanup all allocated resources in the right order when your application terminates either normally or with an error.

Development

Build Status Hackage Dependencies Github

This library is intended to be minimal, providing a few functions that work reliably among many different kind of projects. If you want to contribute, Pull Request are very welcome! Please try to follow these simple rules:

  • Please create a topic branch for every separate change you make.
  • Update the README.md file if necessary.
  • Please do not change the version number on your Pull Request.

Open Commit Bit

This project has an open commit bit policy: Anyone with an accepted pull request gets added as a repository collaborator. Please try to follow these simple rules:

  • Commit directly onto the master branch only for typos, improvements to the README and documentation.
  • Create a feature branch and open a pull-request early for any new features to get feedback.
  • Make sure you adhere to the general pull request rules above.

License

Copyright (c) 2017-2018 Roman Gonzalez

Permission to use, copy, modify, and/or distribute this software for any purpose with or without fee is hereby granted, provided that the above copyright notice and this permission notice appear in all copies.

THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.