Content area
Vogt discusses the evolving batch processing to keep pace with modern DevOps. Batch processing simply refers to the processing of transactions in a group or batch. This is different from real-time transaction processing, which happens one transaction at a time. Consider the example of an ecommerce purchase -- behind the customer's real-time transaction is a series of ancillary tasks associated with orders being placed, which might not happen right away. These tasks may include inventory replenishment that may not occur immediately, especially for products that are purchased early in the day and/or sell by the tens or hundreds of thousands daily. There are numerous reasons -- often related to cost and warehouse efficiencies -- that these processes occur in bulk as part of batch processing jobs once orders reach a certain threshold. Batch processing is the key to many of these supporting back-end processes. But at precisely the time the proliferation of modern apps is placing greater demands on batch processing, the industry is also facing a retiring workforce of batch operators. It is imperative for batch processing to modernize alongside the real-time software products that are emerging from DevOps.