MongoDB is the most common NoSQL database you will think of when you think about it. MongoDB is synonymous with programmers as “NoSQL”, but there are many other types of NoSQL databases. Microsoft, for example, offers data lake services. Data lakes are huge pools of non-relational data that are ideal for ‘big data’. However, querying MongoDB is not the same as accessing data stored in a data lakes. How can you access Azure non-relational data? This is what we will be discussing today.
Although Microsoft offers traditional NoSQL databases such as MongoDB, data lakes can be a completely different beast. Azure’s non-relational data storage uses proprietary storage methods and database engines. Access to non-relational Azure information is also possible using the Microsoft IAM (identity management and access management) systems. Non-relational data can also be stored in the Microsoft storage system.
It will be simple to create a non-relational Azure data store if you are familiar with how Azure services work. The process isn’t difficult if you are familiar with Azure services. However, you must understand how cloud services such as Azure work.
Azure and other cloud services offer a variety of services, but they are all based on central systems. Data storage and IAM services are two of those systems. These services are used by Microsoft to create other products, such as CosmosDB.
Microsoft Azure Architect Technologies (AZ-303)Related Training from SPOTO
Start trainingAll services offered by Azure are linked in some way. All Azure services use IAM to grant user permissions. These permissions specify who is allowed to use which services. Similar to Azure’s storage system, other Azure services can also use it to store data.
Below, we will provide more details on non-relational Azure data system requirements for you to be in a position to access them.
An Overview of Accessing Azure Data that is Not Relational [VIDEO]
SPOTO trainer Ben Finkel demonstrates how to access and secure non-relational data within Azure. There are steps you can take to ensure that your non-relational data is available and secure in Azure. These steps are similar to those for other Azure resources. Learn how to manage security and access using data encryption, user authentication, and firewalls – all in Azure.
NoSQL Azure Data are Encrypted at Rest & in Transit
All data stored in Azure is encrypted. Azure offers different levels of encryption and encryption management. However, Azure maintains a minimum level security.
All data is encrypted at rest in the SQL database, which is one of the minimum levels of security. This means that any data stored in Azure storage is not processed or transmitted and is encrypted while it is just sitting there. This protects data from being accessed by others.
This has implications for developers. Organizations will need encryption keys to manage. Data will be lost if those keys are lost. Microsoft offers companies the option of managing encryption keys themselves or letting Microsoft manage them.
Azure’s non-relational database data is stored somewhere. That somewhere is Azure storage systems. Data storage in Azure can also be encrypted. You can choose what data to encrypt when you create a non-relational Azure database. You can choose to encrypt only data files and blobs at rest.
You have the option to encrypt the entire infrastructure. This decision must be made at the time of creating the database. It cannot be modified later.
All connections to Azure are made via HTTPS. This means that all data is encrypted during transit. This cannot be turned off.
Role-based access control can be used to restrict NoSQL Azure data
Traditional relational databases come with their own user management systems. These are primarily legacy databases.