Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/kowainik/cake-slayer
🍰🔪 Architecture of Haskell backend applications
https://github.com/kowainik/cake-slayer
architecture backend elm haskell haskell-backend web
Last synced: 3 months ago
JSON representation
🍰🔪 Architecture of Haskell backend applications
- Host: GitHub
- URL: https://github.com/kowainik/cake-slayer
- Owner: kowainik
- License: mpl-2.0
- Created: 2019-09-20T06:24:00.000Z (about 5 years ago)
- Default Branch: main
- Last Pushed: 2023-01-11T07:12:15.000Z (almost 2 years ago)
- Last Synced: 2024-06-18T00:41:04.454Z (5 months ago)
- Topics: architecture, backend, elm, haskell, haskell-backend, web
- Language: Haskell
- Homepage: https://kowainik.github.io/projects/cake-slayer
- Size: 46.9 KB
- Stars: 131
- Watchers: 8
- Forks: 6
- Open Issues: 7
-
Metadata Files:
- Readme: README.md
- Changelog: CHANGELOG.md
- License: LICENSE
- Codeowners: .github/CODEOWNERS
Awesome Lists containing this project
README
# cake-slayer
[](https://github.com/kowainik/cake-slayer/actions)
[](https://hackage.haskell.org/package/cake-slayer)
[](http://stackage.org/lts/package/cake-slayer)
[](http://stackage.org/nightly/package/cake-slayer)
[](LICENSE)
`cake-slayer` (do not confuse with `cakes-layer`) is a modern and
batteries-included framework for creating backend in Haskell for
web-applications. It allows you to scaffold working and extensible project in
minutes.
## Overview
The main goal of `cake-slayer` is to provide a backbone for your Haskell
backend. Unlike many other Haskell libraries, `cake-slayer` doesn't try to be as
abstract as possible. It includes best-practices and makes some architecture
decisions for you. On the one hand, your application should satisfy the
requirements for using this framework. On the other hand, it takes care of a lot
of stuff for you, so you don't need to worry about everyday problems.
A typical backend does the following:
* Communicates with the frontend (web, mobile) via some wire format (JSON,
Protocol Buffers, etc.)
* Talks to the database
* Authenticates and authorizes users
* Has some background jobs
`cake-slayer` works exceptionally well if your application uses:
1. PostgreSQL as database.
2. Elm on the frontend.
The following Haskell packages have been chosen to provide the necessary
functional:
* [`postgresql-simple`](https://hackage.haskell.org/package/postgresql-simple),
[`postgresql-simple-named`](https://hackage.haskell.org/package/postgresql-simple-named),
[`postgresql-simple-migration`](https://hackage.haskell.org/package/postgresql-simple-migration)
+ For connecting and talking to the PostgreSQL database
* [`servant`](http://hackage.haskell.org/package/servant),
[`servant-swagger`](http://hackage.haskell.org/package/servant-swagger),
[`swagger2`](http://hackage.haskell.org/package/swagger2)
+ A family of libraries for defining and documenting Rest API using type-level eDSL
* [`elm-street`](http://hackage.haskell.org/package/elm-street)
+ The bridge between Elm and Haskell — generating Elm data types, JSON
encoders and decoders from Haskell types automatically
* [`jwt`](http://hackage.haskell.org/package/jwt)
+ User authentication via JWT
* [`bcrypt`](http://hackage.haskell.org/package/bcrypt)
+ Secure password hashing
* [`ekg`](http://hackage.haskell.org/package/ekg),
[`prometheus-client`](https://hackage.haskell.org/package/prometheus-client)
+ Application performance monitoring.
> **NOTE:** Using `prometheus-client` is optional
Besides `cake-slayer` encourages (but doesn't force) to use the following libraries:
* [`relude`](https://hackage.haskell.org/package/relude)
+ Alternative standard library
* [`co-log`](https://hackage.haskell.org/package/co-log)
+ [Composable contravariant comonadic logging library](https://kowainik.github.io/posts/2018-09-25-co-log)
## How to use?
The `cake-slayer` framework contains implementations of most common and useful
functions. But at the same time, it provides enough flexibility to specify
application-specific parts. To integrate `cake-slayer` smoothly into your
project, you should perform the following steps:
1. Define a type of errors your application can throw. See `CakeSlayer.Error`
module for details.
2. Define a monad for your application by specializing the `App` monad from the
`CakeSlayer.Monad` module.
3. Derive or implement all necessary instances for your application monad.
`cake-slayer` provides `MonadJwt` and `MonadTimed` effects with sensible
default implementations for your convenience.
And you're good to go!