Batch jobs are essential for many applications but sometimes there is too much hassle to stop and re-enable them when needed. We are going to see what they are, the scenarios in which it is needed and how to use a standard microservice pattern to address it.
As applications grow it is normal to break them down into smaller pieces that are easy to combine and maintain. The challenge comes in the integration between these pieces as an small change in one of them may break the communication with the others, and we may not notice it until we get emails from users. We are going to see how to detect this automatically using contract testing.