One of the solutions for which a microservice serves a very useful purpose is that of scheduling jobs. If you follow a true separation of concerns pattern, separating this functionality into its own business unit, that is, a microservice, is the correct thing to do. In this chapter, we are going to create a microservice that does just that. We will also gain exposure to Quartz.NET, a fabulous open source job scheduling platform.
The difference with this microservice over others is that it does not accept or respond to messages. Even though that is the heart of our ecosystem, I want to show you that there's no harm in having a mix of microservices doing your work. Not everything needs to have or send a message. This microservice will be your job executor that is performing pre-defined work. Can it send and accept messages? Absolutely. You...
