Fundamental Information for Azure Open Source Databases


As all of us know that Microsoft Azure Supporting many different database types such as Azure SQL, Azure Cosmos DB, and Azure support also MariaDB, MySQL, and PostgreSQL so it easily to migrate your current database (MariaDB, MySQL, and PostgreSQL) to Azure , in this post i will share Fundamental information about MariaDB, MySQL, and PostgreSQL on Azur

  • For more information About Azure SQL Check this Link
  • For more information About Azure Cosmos DB check this link
  • For more information About Azure Exam ( Az-103, DP-200, DP-201, DP-900, DP-300)preparations Check this link
  • For more information About other Azure Services check this link
Microsoft Azure Open Source Databases

MariaDB, MySQL, and PostgreSQL on Azure

  • Microsoft Azure Offers 3 different open source Database Platform on Azure (MySQL, MariaDB, PostgreSQL) and this 3 Database platform service comes with native high availability, automatic patching, automatic backups, and the highest level of security protection
  • Service Tiers Supported by open source Database Platform on Azure
  • Basic: Best of a light workload
  • GP (General Purpose): Best for High Workload required high IO
  • Memory-Optimized: Best for High Workload required high performance and in-memory speed.
  • Supported version for open Source database platform on Azure
  • MySQL and MariaDB on Azure Transactions on either platform are written synchronously to storage. If a node interruption occurs, the database server will automatically create a new node and subsequently attach the storage to the new node. Any transactions in flight are not committed and active connections to the database are dropped. As mentioned with Azure SQL Database, it is important to ensure that applications that connect to the database service include retry logic, also known as connection resiliency, in their database connections.
  • Database migration can be done for 3 open source database platform using Microsoft DMS Azure Database Migration Service
  • Azure SQL Database for MySQL and PostgreSQL does not have a TDE: But Microsoft provided a disk encryption method.
  • Azure PostgreSQL Deployment Model (Single Server, Flexible Server {Preview} or Hyperscale {Citus})
  • Flexible Server, a new deployment option now in preview for Azure Database for PostgreSQL and Azure Database for MySQL, offers customers enhanced choice, performance, and scale by building on a new architecture with native Linux integration “Ignite 2020 News
  • Azure PostgreSQL Hyperscale used for large-scale databases that scale-out across multiple nodes
  • Azure PostgreSQL Hyperscale Server Called Nodes and it is working together in a shared-nothing
  • And the nodes are added to the Server Group
  • Each Server group have something called a coordinator node and multiple workers nodes
  • When the APP Sends the Transaction to Azure PostgreSQL Hyperscale, it sends it to the coordinator node and the coordinator node will find the worker nodes to collect the data to the APP.
  • Azure PostgreSQL Hyperscale is sharded, this means the data in a table can be split into multiple nodes using a type of table called a distributed table.
  • During the Deployment of Azure PostgreSQL Hyperscale Microsoft allow you to create additional worker nodes along with a coordinator node
  • You can deploy Up to 20 worker nodes and in case if you need more you should communicate with the Microsoft support team
  • You can connect to Azure PostgreSQL Using SQL or pgAdmin Clint
  • More information Check Documentation: https://docs.microsoft.com/en-us/azure/postgresql/
  • Query Store Supported in Azure MySQL https://docs.microsoft.com/en-us/azure/mysql/concepts-query-store

Azure Cosmos DB High Availability and Disaster Recovery Architecture


Part 6 in Azure Cosmos DB architecture Series Keep Learning and Spread your Knowledge if you don’t read the previous parts I highly recommend you to take a look into them:

Continue reading “Azure Cosmos DB High Availability and Disaster Recovery Architecture”

Azure Cosmos DB API Architecture


Again, still we have a lot of information we can spread our knowledge on it for Cosmos DB today I will talk about Cosmos DB API options and How I can choose between them and what is the key factor I should consider it when I choosing the Cosmos DB API. IF you don’t read my last articles in Azure Cosmos DB so here is your road map to learn Cosmos DB:

Continue reading “Azure Cosmos DB API Architecture”

Consistency Architecture in Azure Cosmos DB


In my first article in Azure Cosmos DB, we talked about What is Cosmos DB and How to provisions it, then in the Second article we talked about Partitioning Architecture in Azure Cosmos DB, then in third Article we talked about Azure Cosmos DB Global data distribution Architecture, today we will complete our series to talk about Consistency Architecture in Azure Cosmos DB For more information about my Azure articles check this link, Keep Following to learn More about Azure and Cosmos DB

Introduction

Microsoft Azure Cosmos DB Provide 5 level of Consistency (Strong, Bounded staleness, Session, Consistency prefix, Eventual) Before Explaining What is Consistency, Why I should take care about Consistency, Which Consistency is best for my APP design before all of that let us talk first about CAP Theorem

Consistency in Azure Cosmos DB
Continue reading “Consistency Architecture in Azure Cosmos DB”

Azure Cosmos DB Global data distribution Architecture


In my first article in Azure Cosmos DB, we talked about What is Cosmos DB and How to provisions it, then in the Second article we talked about Partitioning Architecture in Azure Cosmos DB. And today we will complete our learning to understand What is global distribution in Azure Cosmos DB? For more information about my Azure articles check this link

When we say global distribution you Should think Automatically in Cosmos DB because it is the most solution in the market provide this feature global distribution, But why global distribution we should be interested in it for couple of reasons unlimited elastic write and read scalability, Yes Cosmos DB provides a solution to read and write option in multiple regions most of the databases solutions provide read scalability but in Azure Cosmos DB we have also write scalability.

Continue reading “Azure Cosmos DB Global data distribution Architecture”