Thanks for this post - it is helpful and aligns with one of the primary uses of SnapLogic for us at Davidson College. I have a few questions…
Is the Ultra task necessary to meet the general requirements of creating an API resource / endpoint or could we use a trigger task? In other words does the Ultra task only address the “low latency” characteristic?
One bearer token per task / endpoint is a bit cumbersome when considering building out an API-based architecture. For example, we want to provide access to multiple resources / endpoints for a single application or consumer via a single bearer token. Is there a tweak to your design pattern which would accommodate this?
Thanks again for this post. I hope to hear back!
~Nick
Ultra tasks allow for low latency, they also allow for data processing to continue when communication with the control plane is broken for some reason, allowing for higher availability.
Using JSON Web Tokens (through the use of JWT Snaps in the pipeline) allows for more control on the tokens. The tokens can be configured with an expiration time, there can be multiple tokens per task, a single token can be shared across tasks in a project or project space etc.
Thank you…
Do we have sample pipelines to demonstrate “2”
The documentation pages for the Snaps have sample pipelines, see JWT Generate and JWT Validate
