Node-RED implements generalised connections manager.
Node-Red generalized connection manager to allow connection pooling and UOW (unit of work) over multiple nodes. Maximizes asynchronous processing which is dependent on driver provider. Some drivers allow for more asynchronous processing. Tries to enable a common framework for connections which includes common pooling and minimization of variance in language implementations. For example for SQL alignment with ISO standard. Should help minimize swap between technologies. Other languages will be evolved as developed.
Currently handles following connection types:
and has been built in a way to readily add more types. Very quick if driver base aligns with deployed type.
Simple example for neo4j connection
Results in msg. Note, example is results for neoj4. For relational connections results standardized. In future, will give option of standardised form versus "as per software provider".
- Connection acquired and used across a series of nodes so transactional UOW can be formed
- More than once connection can be involved in UOW
- Releases a connection if it has not been released for a minute. Cater form work flows that have not properly completed or unexpected error
- Works with PostgreSQL, neo4j, Cassandra, Db2, Monetdb and DataStax.
- Simple data mappings
- Array input for multiple execution of statement. Useful for bulk loads
- The one statement and set of values can be sent to multiple connections
- Aggregation of results into one form across multiple connections
- Mustache template for statements
- postgres parameter markers as ? in line with ISO
- Optional one form of result output regardless of driver type which is aggregated
- Connection Manager - Configuration of connection pool including size
- Get Connection - acquires a connection for the work flow
- Release Connection - releases all connections back to pool
- Statement - statement to be executed against connection pool or all connection pools
- Admin Connections - get details on pool and manage pool
Nodes in Detail
Configurations nodes that can be accessed via get connection.
Get a connection for a message and adds to the message as a property. A message can have many connections. Connection is used by all subsequent statement nodes.
Releases all connections from a message and frees connections to be used by new messages. Message can be committed or rolled back to checkpoint, All statements executed from get connection can be formed as part of UOW.
The statement will be executed against connection associated with the message.
This can be minimized to only one of the connections by detailing the connection name.
Mustache template for statements per message or once at node start.
Message has access to msg.
This node takes in actions specified by the topic. Valid actions:
- list - Output payload contain metrics on connection pools
- releasestale - Puts connections that appear to be active back into pool
- releaseFree - releases connections from pool that are free
- toggleDebug - Sends more debug information to system log
In future will be used as a means of dynamically changes certain properties such as pool size.
Data-Stax Cloud Connection
Generate the secure-connect zip file from DataStax and update options file as follows:
To Do List
- Add transactional - option on connection manager and release to have commit/rollback
- Standardised results format, at moment default of driver
- Access performance metrics
- Dynamically change size of pool
- Wait on connection to become free
- Configurable stale connection cycle
- Specific Mustache properties to allow for DBMS variance, e.g. "limit" vs "fetch first"
Run the following command in the root directory of your Node-RED install
npm install node-red-contrib-connectionmanager
Test/example flow in test/generalTest.json
Note The examples will require the drivers to be installed
0.1.4 Bug fix for bug fix
0.1.3 Bug fix node-red depreciated features on nodes-started, added initial test connection test, timeout for postgresql rather than wait indefinitely
0.1.1 Bug fix commits DataStax and Cassandra as concept doesn't exist
0.1.0 Add DataStax and Cassandra. Include drivers rather than separate install. Add limited mustache on statements. Performance metrics.
0.0.7 Use new feature in postgresql to return columns as array
0.0.6 fix bug with postgresql when parameters > 9.
0.0.4 fix bug on statement.
0.0.3 fix bug with error handling and arrays. Add pg in to package dependencies. More debug details.
0.0.2 get rid of monetdb warning. Add in access to flow.get env.get, global.get