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

Coordination service


In a distributed system, we need to maintain configuration information, and possibly provide distributed synchronization and group services, such as group membership and leader election. A lot of work is required every time any of these services is implemented. All this is taken care of by a Coordination Service. A coordination service is responsible for centralizing all these configurations and maintenance services. A coordination service's primary job is to help multiple nodes work together seamlessly:

Here are some characteristics of a typical coordination service:

  • Is replicated over a set of machines (Servers) for availability and fault-tolerance
  • All machines store a copy of the data, usually in-memory (for high-throughput and low latency) and in persistent transaction logs (for fault-tolerance)
  • The servers of the Coordination Service must know about each other
  • A leader is elected on service startup
  • Clients should connect to a single server within a coordination service...