Booture uses Hooks (as you might expect) to ensure that whatever happens,
once a service is acquired, it will always be disposed. Furthermore,
acquisition and disposal of services happens at optimal parallelism.
Booture exposes a single function: bootstrap, which in
combination with Fluture and Fluture Hooks, provides an ideal
platform for control over your application lifecycle.
This file adds booture to the global scope, or use CommonJS/AMD
when available.
Usage Example
The example below defines four "services": config, postgres, redis,
and app. The App depends on Redis and Postgres having been initialized,
which in turn depend on the Config service.
The consumption of these services happens in the form of binding the App to
a port, and waiting for SIGINT to complete the consumption.
Some things to note about the example above, and general usage of Booture:
servicesHook is a Hook, so before running it, it can be composed
with other hooks using map, ap, and chain, and even used in the
definition of other bootstrappers.
program is a Future, so nothing happens until it's forked. Before
forking it, it can be composed with other Futures using map, ap,
bimap, and chain, or any of the other functions provided by Fluture.
API
Types
type Name = Stringtype Services a = Dict Name adata Bootstrapper a b = Bootstrapper { name :: Name, needs :: Array Name, bootstrap :: Services b -> Hook (Future c a) b}
Given a list of service bootstrappers, returns a Hook that represents the
acquisition and disposal of these services. Running the hook allows for
consumption of the services.