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

System design and assumptions


There are basically two parts of the email system:

  • Email sender
  • Email tracker

I am going to show you, in a small block of code, how to send an email using Node.js with the tracking code inside the email. However, it won't be production grade (this is our assumption).

The email tracker, however, will be a production-grade design; this tracker will receive the event from the email and update the database accordingly. We will discuss which database API to use and everything else in the upcoming section.

Now, for the sake of design, here is a diagram:

As you can see in the preceding diagram, the email sender will pick up the record from some source which will contain an email list and send out emails to lots of people.

When people open, click on, and read those emails, the email tracker will track those events and record them in the database.

Now, system design is not just the diagram design; it has lot of things within it, such as capacity estimation, database diagrams...