A fundamental feature of any system is that when starting to design a batch layer, we should always try to divide the business logic into meaningful chunks that adhere to the single responsibility principle. Even though, at a high level, there are essentially three steps in a batch application, namely read, process, and write, there are some caveats we need to keep in mind when implementing the business functionality. It will also help understand the subcomponents of the batch layer. Let's talk about them in a bit more detail.