Session
Where we're going... we don't need batch jobs
Ever write a batch job? Batch jobs are bits of code that periodically look at your database’s current or historic state and then act on it. They often run off-hours or in the middle of the night to avoid performance impact, and if they fail while processing, get ready for a pager alert. You can prevent this nightmare by telling your system what to do in the future! Look to the real world to model a long-running business process from start to finish.
Join me and learn:
- The challenges with recurring batch jobs.
- How to move a business process away from batch processing.
- Real-world use cases for modelling future events.
Adam Ralph
Distributed systems expert at Particular Software
Flims, Switzerland
Links
Please note that Sessionize is not responsible for the accuracy or validity of the data provided by speakers. If you suspect this profile to be fake or spam, please let us know.
Jump to top