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

Architectural patterns


A pattern is simply a template that can be applied to solve a specific set of problems. As you can imagine, a pattern is simply a blueprint of what could be done. It is up to the implementer to apply and implement the pattern.

We can also think of architectural patterns slightly differently. When we observe something in our current architecture that we believe can be reused elsewhere, we extract that out and capture the design ideas as an archetype. The design patterns are always, or should always be, technology-independent. If a pattern can only be implemented using a specific technology, it usually is not a pattern but just a technology-specific problem.

The following is not an exhaustive list of architectural patterns, but a collection of patterns and traits of existing systems that are successfully designed following the Architectural Principles we defined in earlier chapters.

Let's start discussing these patterns in a little detail.

The retry pattern

A retry pattern...