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

Reliable messaging


Another important aspect of a Distributed Data Intensive System is reliable messaging. By reliable messaging, we mean that if a message publisher publishes a message, then we provide him with a guarantee that the message will not be lost during transit. It does not mean that the message is successfully consumed by the consumer. What it means is that the messaging system will not lose the message for an agreed SLA time duration. If the consumer is not able to consume the message within the SLA, it is up to the messaging system to decide what to do with the message. The message can be permanently deleted, put in a Dead Letter queue, or persisted outside of the messaging system.

Reliable delivery requirements also vary from system to system. There are usually three types of Reliability guarantees that an application would require, they are as follows:

  • At-least-once delivery: This requirement states that a message published by a publisher should be delivered at least once to...