Book Image

Architecting Data-Intensive Applications

By : Anuj Kumar
Book Image

Architecting Data-Intensive Applications

By: Anuj Kumar

Overview of this book

<p>Are you an architect or a developer who looks at your own applications gingerly while browsing through Facebook and applauding it silently for its data-intensive, yet ?uent and efficient, behaviour? This book is your gateway to build smart data-intensive systems by incorporating the core data-intensive architectural principles, patterns, and techniques directly into your application architecture.</p> <p>This book starts by taking you through the primary design challenges involved with architecting data-intensive applications. You will learn how to implement data curation and data dissemination, depending on the volume of your data. You will then implement your application architecture one step at a time. You will get to grips with implementing the correct message delivery protocols and creating a data layer that doesn’t fail when running high traffic. This book will show you how you can divide your application into layers, each of which adheres to the single responsibility principle. By the end of this book, you will learn to streamline your thoughts and make the right choice in terms of technologies and architectural principles based on the problem at hand.</p>
Table of Contents (18 chapters)
Title Page
Packt Upsell
Contributors
Preface
Index

Batch layer components and subcomponents


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.

Read/extract component

As you know, this is the first functional component that is part of the batch layer. For every operation/conversion/processing that you to read the data on which the action needs to be performed.

 

Normalizer component

A conversion component is responsible for taking the data from one type of representation to another type. For example, the processing component of your batch layer might require you to apply...