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

Data collection system architecture principles


In the following section, we will discuss various architectural principles that are advised to be adhered to while designing a data-collection system:

  • Modular service-oriented System

The capabilities of the data-collection system shall be offered as independent services that can be consumed over HTTP protocol.

  • The system should be Distributed in nature

Different components and services within the system should be deployable on different nodes, irrespective of the node's locality. These nodes can be intra Data Centre, inter Data Centre, or across continents. The application as a whole should be agnostic of the network deployment of the components within the application.

  • The system should be resilient to failure

If and when a failure occurs within the data-collection system, the system should not go down like a house of cards. Instead, the system should be built such that it can handle failure gracefully. The system should anticipate, respond to, and...