Low latency Ultra

This design is for pipelines that use a request and response construct.

• One unconnected input view
• One or more unconnected output views
• A FeedMaster is required in the Snaplex.

This design acts as a data access layer for real-time web services, transforming a pipeline into a continuously running job. Documents are fed into the pipeline through a FeedMaster, which queues the documents. The pipeline processes these documents and returns responses via the FeedMaster.

For use cases, pipeline design guidelines, and examples, see Low-latency Ultra Tasks.

Headless Ultra

This design is for pipelines that require continuous data flow.

• No unconnected input view and no unconnected output view
• A FeedMaster is not required.
• This setup is typically used if the data source is a Snap such as JMS Consumer.

This design is often used in a listener-consumer construct. An Ultra Task with no unconnected views can continuously poll and consume documents from an endpoint without requiring a document feed from the FeedMaster.

For use cases, supported listening Snaps, and examples, see Headless Ultra Tasks.