JD has a webhook implementation Data Subscription Service (DSS) that looks quite robust: https://developer.deere.com/dev-docs/webhook#getting-started
Before we really consider using Drupal cron as a way to do real time updates I think we should really consider webhooks. In some ways it is likely more work, but it would really solve many problems. When I first saw that they had webhooks I was cautiously optimistic, worrying that it might not be robust enough to fully depend on. But reading a bit closer now, I like that it does have some retry + query failover mechanisms. In conjunction with Drupal cron we could do daily checks to 1) ensure all subscriptions are "healthy", maybe automatically remedy 2) possibly perform batch imports daily, if we cannot do 100% real-time imports
Needs more thinking, but just putting it out here that I think this would be worthwhile.
N/A
Investigate, implement
Some additional UI to show that subscription status/health
Add API for receiving event updates
Likely need some new places to store this info, perhaps a mix of Drupal config/temp store + a database table for actual event changes
Active
1.0
Code
Welp, not everything has an associated webhook/event associated with it in JD (like Machines). So we can't do everything via webhooks, but likely most things. Full list of events here: https://developer.deere.com/dev-docs/webhook#events