Extensions are SPARKL applications that provide the core functionalities of the SPARKLĀ® Sequencing Engine. These applications can be used by referencing them in the markup of services. It is also possible to extend the core functionalities by adding optional extensions.

Table 1. Service provisioning with SPARKL extensions
Attribute value Core or optional Description
tabserver Core extension Services provisioned using the Tabserver extension run in your browser.

Services provisioned on Tabserver depend on a tabserver_connection service being up.

tabserver_connection Core extension Services provisioned using tabserver_connection accept connections from browsers.

Services provisioned using tabserver depend on such a service.

sequencer Core extension Services provisioned using the Sequencer extension can process transactions.
expr Core extension The Expressions extension supports the use of Erlang expressions in SPARKL.
subr Core extension The Subroutine extension supports subroutine transactions called by a caller operation.
Note: The subroutine specification is defined on the caller and callee operations on the svc_subr service.
lambda Core extension This service extension integrates AWS Lambda functionality into SPARKL mixes allowing you to run Node.js and Python scripts in a serverless architecture.
Note: See Lambda AWS documentation for further details.
phidget Optional extension The Phidget extension allows you to map Phidgets sensors, motors and interfaces to fields.

Extensions can be viewed, started and stopped in the Node Elements view of the Developer Console.