Apr 1, 2021, 12:30 – 2:00 AM (UTC)
When synchronizing data between two systems, occasionally, data for a child object arrives at the target system slightly before the parent object creating a referential integrity error. Ideally, the child object should be resent to the target after the parent object arrives. We will show you how to implement the solution to ensure referential integrity.
There are occasions when synchronizing data between two systems that a child object arrives at the target system slightly before the parent object. When this out-of-order object arrives, a referential integrity situation occurs. How to solve it?
Tim Hanline from Mule Learning will join us to build a delayed reprocessing algorithm using queues and a scheduler. He will point out where a developer must take special care with the queues' configuration in order to successfully reprocess errant messages on a time delay. Tim will build this solution from scratch, with the goal of all meetup participants leaving the meetup with a working delayed reprocessing solution.
** If you wish to develop the solution during the Meetup, please have Anypoint Studio 7.x installed. We will do our best to resolve any issues you are having via Chat.**
***PLEASE NOTE: In order to join this event, you must "Login" to the meetups.mulesoft.com website. You will then be able to join. You can NOT join directly from the URL provided in the Meetup email.***
CloudBlazer
MuleSoft Practice Lead
Argano
Director - Delivery, MuleSoft Practice
Argano
Meetup Coordinator
Big Compass
Cloud Practice Manager
Thursday, April 1, 2021
12:30 AM – 2:00 AM (UTC)
| Attendees join Meetup |
| Introductions |
| Building the Delayed Message Reprocessing Solution |
| Wrap up and next Meetup |
| Meetup concludes |
Contact Us
