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

Lambda architecture


We are talking about Data-Intensive Systems. But what is the main purpose of developing a Data-Intensive System? What does a Data-Intensive System really do? You may say it processes the data at scale, but still that's just a step in the actual question that it is trying to answer. A Data-intensive system tries to answer questions based on the data that is either presented to it in real-time, on the data that have been collected in the past, or a combination of both. BigData, a book by NathanMarz, defines Data Systems as systems that compute queries that are functions of all the data we've ever seen:

Query = Function(all data)

This definition of a query is at the center of Lambda architecture.

The first thing that should come to your mind is depending on whether Query is always the function on all data, and whether the data is in terabytes or petabytes, how do our queries perform? What are the latencies and requirements around it? Another important thing to consider is the...