Consume Events Using the Journaling API
This Code Lab will guide you through creating cron jobs in an App Builder application to consume events using the Journaling API.
User story
There is a class of App Builder apps for which customers want guarantees that I/O Events will be processed without losing any, for example during a surge of events. Without processing guarantees, a Runtime webhook would return a 429 response when it passed its concurrency limit, causing the webhook to be marked unreachable and ending delivery of events. The Journaling API of custom events resolves this situation.
Solution
- Use the Journaling API to retrieve events instead of relying on the webhook approach.
- Use a Runtime action that uses the Alarm package to read the events every X minutes.
- The alarm action stores the events in the App Builder storage aio-lib-state
- Record an index of events in storage so that if the action fails, the next invocation will retrieve from the same index, and no events will be lost.
This Code Lab provides an end-to-end solution that demonstrates how to use the Journaling API to consume events. It includes:
- Event provider to generate events automatically and send them to the Journaling API. If you already have an event provider, you can skip this step.
- Event consumer, the most important demonstration in this Code Lab. We will create another App Builder headless app to create cron jobs with alarms, and set up recurring jobs to pull from the Journaling API every x mins and write into App Builder storage.
Event provider and event consumer both need to be deployed as App Builder apps under different namespaces to endsure end-to-end workflow. If you don't have them already, create two projects at Console following the steps detailed in Creating your First App Builder Application.
When they are successfully set up, you should be able to see your event consumer periodically pull events from the Journaling API and write them into storage. For your convenience, there is a complete solution of this Code Lab here.
