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

An introduction to ETCD


We have talked a little about ETCD here and there through this chapter, but we haven't detailed what it is being used for and why we need it.

This section talks briefly about ETCD and its function as the distributed configuration-management service for our data-collection System. The motivation behind having a distributed application configuration-management System is the following:

  • Globally accessible application configuration store
  • Decouple the application configuration information of a system from the actual code
  • A single place to store the application configuration information for the application as opposed to storing the configuration as JSON per instance of the application
  • Provides the ability to build intelligent endpoints for updating runtime configuration changes on the fly, without the need to restart the application or deploy configuration changes by restarting the applications automatically
  • A single place for configuration information about different environments...