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

Processing concepts and tradeoffs


When developing a stream-based system, it is not only sufficient to understand the technologies that will enable the development of such a system, it is also important to understand how you will handle certain implicit and/or explicit requirements that focus mainly on the nonfunctional side of the spectrum. In this section, we will dive deeper into some such requirements.

Processing guarantees

When developing a stream processing application, you need to first understand how, and whether at all, you would be able to handle loss of data. Imagine a situation where a processing job has acknowledged the receipt of an event for processing, it has processed the event successfully, but before giving the message to the next-in-line processor, it fails. In Stream processing, this is the most often-asked scenario:

Does the underlying stream processing system guarantee that each event will be processed once and only once, even though there are failures at various stages...