What are Azure Data Storage services/options?

These are the databases that most people are likely to be familiar with, as well. Azure SQL is now in place. When it comes to SQL Server, this is a cloud-based version, if you will. However, there are a wide range of options to choose from across the entire spectrum of possible outcomes. You can easily migrate from SQL Server on-premises to a managed instance. In situations where you have a large number of databases but want them to all share the same resources, you can use elastic pooling or Software as a Service (SaaS). There are a lot of ways to use it in the cloud. You can also use MySQL, MariaDB, and PostgreSQL as relational databases. The self-hosted or service-based model has all of these options. It's possible to run any of these on a virtual machine or container, but you can also go out and provision an instance of this and focus on your application development and your data storage, which is a service-based model. All of these are cloud-based, scalable, available, and global in their deployments, and all of them are built for the cloud. When you begin building applications, you have a variety of data storage options to choose from, including relational data. Your table storage is a critical component of your system. In order to identify a collection of data, you need a set of unique keys and corresponding properties or values. If you need to store large objects, such as files, we have blob storage available. Images, PDFs, and other types of documents can serve as virtual hard drives on blob storage, which is optimized for the cloud and the web and includes features such as caching and metadata storage. Azure queues are available for storing messages that need to be passed between nodes in your application for a short period of time. It's also possible to use the Redis cache and other caching options for that in-memory storage in order to save money and improve performance in some cases. With the self-hosted options, I mentioned that you could provision a MongoDB document database in a virtual machine, and you can do that. If you want to build a graph database, you can use Cassandra or Neo4j. A wide range of data storage options, from documents to graphs and columns, are available as self-hosted options. This is because Microsoft's Azure Cosmos DB contains everything you might be looking for in a service-based environment such as MongoDB, Cassandra, or Neo4j. This is a one-of-a-kind database in that it allows for the storage of multiple model types. A graph database in Azure Cosmos DB can be specified when the database is created. It's also possible to use the Gremlin API to access the graph database. To access the data, you can either store it in a table storage model, or you can use any of the Azure SDKs to access it. You can use the Cassandra APIs to interact with your datastore if you set it up as a Cassandra instance. Alternatively, you can create a document database and manage documents using either the MongoDB SDK and protocols or the Microsoft API. For example, if you want to store your data in a service-based model, this gives you the ability to do so in a variety of ways. The fact that Azure Cosmos DB is a globally distributed database in addition to being multi-model makes this a viable option. To put it another way, this means that you can have multiple masters in different regions, as well as low-latency synchronization between the different nodes. Consistency is usually sacrificed for speed when using a system like this because of the trade-off between instantaneous and long-term consistency. Azure Cosmos DB, on the other hand, offers a sliding scale of five different levels to accommodate your various needs. With Azure Cosmos DB, it's possible to choose the data model and APIs you want to interact with the data store, as well as a globally distributed system that's built for the cloud, so you get the best of both worlds. When discussing data storage, I'd like to mention Azure Data Lakes, and here I'm referring to version 2 of this service. Because this is a large-scale data storage designed for analytics and analytics tools, we are now moving toward analytics. On top of Azure Blob Storage, it has two different access models: file-based and blob-based, respectively. It's not just a matter of stacking one model on top of the other, either. They've actually optimized both so that analytics tools can access files or blobs in this data lake using a file-based model and get the same level of performance as a blob API. This means that you get the benefits of blob storage and all that comes with it, including the ability to put data into an archive or cold storage that you don't use as frequently to save money. To illustrate this, we've provided a number of different options, all of which have been built with cloud-scale application development in mind.

Видео What are Azure Data Storage services/options? канала EduFi