eventstore: EventStore TCP Client

[ bsd3, database, library ] [ Propose Tags ]

EventStore TCP Client

[Skip to Readme]
Versions [RSS] [faq],,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,, 1.0.0, 1.1.0, 1.1.1, 1.1.2, 1.1.3, 1.1.4, 1.1.5, 1.1.6, 1.2.0, 1.2.1, 1.2.2, 1.2.3, 1.2.4, 1.3.0, 1.3.1, 1.3.2, 1.3.3, 1.4.0, 1.4.1, 1.4.2 (info)
Change log CHANGELOG.markdown
Dependencies aeson (>=0.8 && <0.11), async (==2.0.*), base (>=4.7 && <5), bytestring (>=0.10.4 && <0.11), cereal (>=0.4 && <0.6), containers (==0.5.*), network (==2.6.*), protobuf (==0.2.*), random (==1.*), stm, text (>=1.1.1 && <1.3), time (>=1.4 && <1.6), unordered-containers, uuid (==1.3.*) [details]
License BSD-3-Clause
Author Yorick Laupa
Category Database
Home page
Bug tracker
Source repo head: git clone git://
Uploaded by YorickLaupa at 2015-12-27T22:09:47Z
Distributions LTSHaskell:1.4.1, NixOS:1.4.1, Stackage:1.4.1
Downloads 37899 total (853 in the last 30 days)
Rating (no votes yet) [estimated by Bayesian average]
Your Rating
  • λ
  • λ
  • λ
Status Hackage Matrix CI
Docs available [build log]
Last success reported on 2015-12-27 [all 1 reports]




Maintainer's Corner

For package maintainers and hackage trustees


Readme for eventstore-

[back to package description]

EventStore Haskell TCP client

Join the chat at Build Status

That driver supports:

  • Read event(s) from regular or $all stream (forward or backward).
  • Write event(s) to regular stream.
  • Delete regular stream.
  • Transactional writes to regular stream.
  • Volatile subscriptions to regular or $all stream.
  • Catch-up subscriptions to regular or $all stream.
  • Competing consumers (a.k.a Persistent subscriptions) to regular stream.
  • Authenticated communication with EventStore server.
  • Read stream metadata (ACL and custom properties).
  • Write stream metadata (ACL and custom properties).

Not implemented yet

  • Secured connection with the server (SSL).


  • GHC >= 7.8.3
  • Cabal >= 1.18
  • EventStore >= 3.0.0 (>= 3.1.0 if you want competing consumers)


$ cabal update
$ cabal install eventstore
  • From source
$ git clone
$ cd eventstore
$ cabal install --only-dependencies
$ cabal configure 
$ cabal install

How to test

Tests are available. Those assume a server is running on and 1113 port.

$ cabal install --only-dependencies --enable-tests
$ cabal configure --enable-tests
$ cabal test

How to use

{-# LANGUAGE OverloadedStrings #-} -- That library uses `Text` pervasively. This pragma permits to use
                                   -- String literal when a Text is needed.
module Main where                                   

import Data.Aeson
-- It requires to have `aeson` package installed. Note that EventStore doesn't constraint you to JSON
-- format but putting common use aside, by doing so you'll be able to use some interesting EventStore
-- features like its Complex Event Processing (CEP) capabality.
import Database.EventStore
-- Note that import also re-exports 'Control.Concurrent.Async' module, allowing the use of 'wait'
-- function for instance.

main :: IO ()
main = do
    -- A common pattern with an EventStore connection is to create a single instance only and pass it 
    -- wherever you need it (it's threadsafe). It's very important to not consider an EventStore connection like 
    -- its regular SQL counterpart. An EventStore connection will try its best to reconnect
    -- automatically to the server if the connection dropped. Of course that behavior can be tuned
    -- through some settings.
    conn <- connect defaultSettings "" 1113
    let js  = "isHaskellTheBest" .= True -- (.=) comes from Data.Aeson module.
        evt = createEvent "programming" Nothing (withJson js)
    -- Appends an event to a stream named `languages`.    
    as <- sendEvent conn "languages" anyVersion evt
    -- EventStore interactions are fundamentally asynchronous. Nothing requires you to wait 
    -- for the completion of an operation, but it's good to know if something went wrong.
    _ <- wait as
    -- Again, if you decide to `shutdown` an EventStore connection, it means your application is 
    -- about to terminate.
    shutdown conn
    -- Make sure the EventStore connection completes every ongoing operation. For instance, if 
    -- at the moment we call `shutdown` and some operations (or subscriptions) were still pending,
    -- the connection aborted all of them.
    waitTillClosed conn


That library was tested on Linux and OSX Yosemite.

Contributions and bug reports are welcome!

BSD3 License

-Yorick Laupa