Summer means vacations and pool time, but we haven't stopped working on Exceptionless 2.0. Things are coming along nicely, and today we're here to talk about the job system and the code being written to enhance it.
After you read this article, check out the previous V2.0 feature and detail articles, if you haven't already. Good stuff in there!
- Exceptionless 2.0 – In the Making
- Event Based Reporting System
- Simplified API
- A Pluggable System
- Exceptionless 2.0 Client Rewrite Sneak Peak and Example
- New Message Bus and Queuing System
- Job System Enhancements
Job System Enhancements #
Jobs can easily be run standalone now, which makes it much easier to test the system. You won't have to worry about your application pool shutting down prematurely and killing your job half way through it's long-running work item.
More Ways to Run #
With 2.0, you'll be able to run jobs in process, as a service, as a standalone exe, or as Azure WebJobs. Cool, huh?
Need More? Run More! #
If you need to process more tasks, simply fire up more jobs. This will save resources and money when using Azure WebJobs, as you can auto-scale jobs based on resource constraints.
We use jobs to send emails, call web hooks, process events, and much more, so these enhancements will allow for better resource control when scaling, and in general.
We've thrown out a lot of information about Exceptionless 2.0 and all the new features, enhancements, and tweaks that it's going to get. We'd love to hear from some of the regulars out there and see if we've missed anything obvious. Check out the links to the other articles at the top of the page and let us know. Thanks!