Book Image

Learning Azure Cosmos DB

By : Shahid Shaikh
Book Image

Learning Azure Cosmos DB

By: Shahid Shaikh

Overview of this book

<p>Microsoft has introduced a new globally distributed database, called Azure Cosmos DB. It is a superset of Microsoft's existing NoSQL Document DB service. Azure Cosmos DB enables you to scale throughput and storage elastically and independently across any number of Azure's geographic regions.</p> <p>This book is a must-have for anyone who wants to get introduced to the world of Cosmos DB. This book will focus on building globally-distributed applications without the hassle of complex, multiple datacenter configurations. This book will shed light on how Cosmos DB offers multimodal NoSQL database capabilities in the cloud at a scale that is one product with different database engines, such as key-value, document, graph, and wide column store. We will cover detailed practical examples on how to create a CRUD application using Cosmos DB with a frontend framework of your choice. This book will empower developers to choose their favorite database engines to perform integration, along with other systems that utilize the most popular languages, such as Node.js. This book will take you through the tips and trick, of Cosmos DB deployment, management, and the security offered by Azure Cosmos DB in order to detect, prevent, and respond to database breaches.</p> <p>By the end of this book, you will not only be aware of the best capabilities of relational and non-relational databases, but you will also be able to build scalable, globally distributed,<br />and highly responsive applications.</p>
Table of Contents (14 chapters)
Title Page
Packt Upsell
Contributors
Preface
Index

Writing our email sender


In practice, the email sender is one of the most complex pieces of our system. I have actually designed an email sender using a queue system to send a huge volume of emails (more than a billion a month) and that is one of the reasons why I am not covering it completely: because it's really very complex.

However, for the sake of an explanation and simplicity, I have designed a simple process diagram of the email sender. Have a look:

Allow me to explain how this works. Queuing is one of the core designs of a scalable distributed system. The queue provides your system with the distribution and communication between your processes.

In our design, I used the queue (message ordering could be your choice, I used First in First out (FIFO) to handle the vast amount of email messages; imagine the volume in the billions and you just can't do a query to a database for that every single time you want to shoot over some emails).

So, the producer here fetches the email records from...