Azure Database

Azure DB gives a organized way to store data in Azure. Azure DB distributes database in multiple zones and regions which gives high availability.
It increases durability by making copies and transaction logs in more than one zones and Azure regions.

Database Categories in Azure

Azure offers multiple database categories to store your data.

Azure SQL Database

  • It gives 99.99 % availability and can store upto 100 TB of data.
  • It is flexible and offers serverless computing.
  • Works well with Microsoft based application.

Azure My SQL Database

  • It is fully managed and scalable database option.
  • While creating MySQL DB in Azure, users can choose single zone or multiple zone redundant.
  • Automatic updates and backup facility available.

Azure Database for PostgreSQL

  • Users can choose single zone or multiple zone to increase the availability.
  • It gives you option for single server and hype scaling.

What is HyperScale ?
It allows to scale database to hundreds of nodes to execute queries.

Read this blog also - 
Microsoft Azure Storage – Benefits, Types and More
Microsoft Azure Fundamentals (AZ-900) Certification Sample Questions

Azure Cosmos DB (Azure No SQL DB)

  • Azure Cosmos provides No SQL DB in Azure
  • Fully managed NoSQL database service by Azure.
  • It automatically replicates data across multiple Azure regions which increases the availability.
  • Azure Cosmos DB is a schema-less DB and offers auto scaling.
  • It supports Mongo DB, JSON, Cassandra, Gremlin (Graph) types of data.

In Memory DB (Azure Cache for Redis)

  • Accessing data from memory is much faster than accessing data from a disk.
  • Azure Cache for Redis offers In-Memory DB based on Redis software.
  • Azure Cache for Redis can be used for Caching, Session management etc.
  • It improves the performance.

DB for Analytics

Azure Synapse Analytics.

Database Recovery terminology

How quickly we can recover data and how much data loss can happen, it decided by below 2 points

  • RPO (Recovery Point Objective) – It is maximum acceptable duration of data loss.
  • RTO (Recovery Time Objective) – It tells about maximum acceptable down time

Data Consistency

  • Strong Consistency – It allows synchronous replication to all stand by databases. The more standby databases you have the slower your transaction will perform. As it replicate data synchronously to stand by database.
  • Eventual Consistency – It is an Asynchronous replication and replicate data to stand by databases with a little lag.
  • Read After Write Consistency – Data insertion are immediately available in stand by DB, however updates follow eventual consistency.

Hope you like this blog. Please follow the blog to get updated notes on Microsoft Azure Cloud Service.

Leave a Comment