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

Chapter 4. Discussing Data-Centric Architectures

So far, we've discussed what a Data Ecosystem looks like, the guiding principles of a Data-Centric architecture, and the application styles and architectural patterns most relevant in Data-Intensive Systems. One of the things that we have mentioned, mostly implicitly, is that Data-Centric architectures are distributed in Nature.

Put simply, a Distributed System is a collection of inter-related components, each having a very specific responsibility, that communicate with each other via a well-defined protocol (such as HTTP or MQ), running on multiple machines (either virtual or physical) that, from the outside, look like a single system.

From this definition of a Distributed System, we can pick up few characteristics of a Distributed System:

  • The different components in a Distributed System have a well-defined single functional responsibility that they perform well and then forward the output of performing the responsibility to the next component...