Kettle is an integration technology which promotes the expression of servers handling HTTP and WebSockets endpoints.
With a few exceptions, Kettle implements no primary functionality of its own, but aggregates the facilities of
express and ws, as well as middleware held in the wider pillarjs
"Bring your own HTTP Framework Framework" ecosystem. Kettle applications can easily incorporate any express-standard middleware, as well as coexisting with standard express apps targeted at the same
http.Server. Since Kettle applications are expressed declaratively, in the JSON format encoding Infusion's component trees, it is possible to adapt existing
applications easily, as well as inserting middleware and new handlers anywhere in the pipeline without modifying the original application's code. This makes
Kettle suitable for uses where application functionality needs to be deployed flexibly in a variety of different configurations.
In fact, Kettle's dependency on express itself is minimal, since the entirety of the Kettle request handling pipeline is packaged as a single piece of express-compatible middleware – Kettle could be deployed against any other consumer of middleware or even a raw node.js HTTP server.
This is packaged as Infusion grades derived from
kettle.app. The first two of these exist in variants specialized both for plain
HTTP (with the
.http suffix) and for WebSockets (with the
.ws suffix) –
kettle.app does not specialize.
As well as the integration technology implementing Kettle itself, this repository also contains functionality helpful for testing HTTP and WebSockets
servers written in arbitrary technologies. This is accessed by running
kettle.loadTestingSupport() after having called
require("kettle"). Kettle testing
support allows HTTP and WebSockets client requests to be packaged as Infusion components, suitable for use with Infusion's
IoC Testing Framework. Any user of Kettle's testing support needs to have node-jqunit
registered as a member of their own project's
devDependencies in their own package.json.
The Kettle repository also contains a few implementations of the simple
DataSource contract for read/write access to data with a simple semantic (broadly the same as that
encoded in CRUD although the current DataSource semantic does not provide explicitly for deletion). See the documentation section
on DataSources for details of this contract, the available implementations and how to use them.
This repository contains DataSource implementations suitable for HTTP endpoints (with a particular variety specialised for accessing CouchDB databases with CRUDlike semantics) as well as the filesystem, with an emphasis on JSON payloads.
Firstly, install node and npm by running a standard installer from node.js. Clone this repository and then run
Issue tracking is at http://issues.fluidproject.org/browse/KETTLE.
#fluid-work on Freenode – community resources are linked at Fluid's IRC Channels.
Contact us on the fluid-work mailing list with any problems or comments.
The primary user of Kettle is the GPII's autopersonalisation infrastructure, held at GPII/universal. Kettle is used to provide a flexible means of deploying the GPII's "Flow Manager" and related components distributed across multiple local and remote installations.
A closely related project to Kettle is gpii-express which is used in other GPII projects such as the terms registry and unified listing. This is similar in architecture to Kettle (wrapping express primitives such as servers and requests into dynamically constructed Infusion components) but slightly different in emphasis –
The request handling architecture for gpii-express and Kettle is quite similar and the projects will probably converge over time. gpii-express currently already depends on Kettle to get access to its HTTP testing support.
Documentation and sample code for working with Kettle is contained in the docs directory. Kettle is based on Fluid Infusion's component model. If you aren't familiar with the syntax and meaning of Infusion component trees, it is a good idea to browse the documentation, tutorials and examples at the Infusion documentation site.
It contains the following topics:
kettle.requestgrouped into app units derived from
Of these elements of this module, those described in topics 1, 5 and 6 (configs, DataSources and the testing framework) are portable and do not depend specifically on the Kettle server and request handling infrastructure – they can be used together with any technologies defining node.js HTTP and WebSockets servers (or in the case of configs, any node.js enabled Infusion application).