Skip to main content

Azure Storage

Azure Storage is Microsoft's cloud storage solution for modern data storage scenarios. 
 Why Azure Storage:
Durable and Highly Available:
·       Data is safe during hardware failure.
·       Replicate data across data centres.
·       In local catastrophe or natural disaster data replicated to other data centres remains highly available.
Secure:
·       Data encrypted by Azure service Storage Service encryption (SSE) for data at rest.
·       Completed control over who access your data.
Scalable:
·       Designed to massive scale.
Managed:
·       Azure handles maintenance, updates and critical issues.
Accessible:
·       Accessible from anywhere in the world.
·       You can access using http, https, .net, java, php, python and etc.
 You can store all type of data
-       Structure:
The term structured data refers to data that resides in a fixed field within a file or record. Structured data is typically stored in a relational database (RDBMS). ... Typical examples of structured data are names, addresses, credit card numbers, geolocation, and so on.
-  Unstructured:
         In the modern world of big data, unstructured data is the most abundant. It’s so prolific because unstructured data could be anything: media, imaging, audio, sensor data, text data, and much more.
Types of Storage Account:
1.     Standard
2.     Premium

1.     Standard:
-       Backed by HDD (magnetic drives)
-       Low cost per GB
-       Used for applications that requires bulk storage.
-       Infrequently accessed data.

2.     Premium:
-       Backed by SSD (Solid State Drive)
-       Low latency performance.
-       Used by i/o intensive applications.
 
Note: You can’t convert standard storage account to premium and vice versa.
 
Azure Storage Services
Azure Storage includes these data services, each of which is accessed through a storage account.
Azure Container (Blobs):
-       Massively scalable object store for text and binary data.
Ideal for:
-       Serving image or document directly to a browser.
-       Storing files for distributed access
-       Streaming video or audio.
-       Storing data for backup and restore, disaster recovery and archiving purpose.
-       Storing data for analysis by on-premises or azure services.
Can be accessed from anywhere in the world using http, https, java, .net, php, python and more.
Azure Files:
Managed files share for cloud or on-premises deployments.
Ideal for:
-       Enable you to setup highly available network file share that can be accessed using server messages block (SMB).
-       Multiple vm’s can share files with both read and write access.
-       You can access the files from anywhere is the world using url includes SAS.
-       You can generate tokens for specific amount of time to have access.
-       Mostly used in on-premises applications, configuration files, or diagnostic log and metrics.
-       Storage account credentials used to provide authentication for access to the file share.
-       Anybody with the share mounted will have read/write access to share.
 
Queue Storage:
A messaging store for reliable messaging between application components.
-       Used to store and retrieve messages
-       Messages can be up to 64kb in size.
-       Can contain millions of messages.
Azure Table storage:
A NoSQL store for schemaless storage of structured data.
-       Part of a azure cosmos DB.
-       Ideal for storing structured and non-relational data.

What is NoSQL:

Please go through below url to understand what is NoSQL

https://www.mongodb.com/nosql-explained

 Storage account kind:

Storage Account

Recommended Usage

Standard General purpose V2

blob, files, queue, table and data lake storage.

Premium block storage

with high transaction rates or scenario that uses
 smaller object or low storage latency

Premium file share

Enterprise or high performance file share applications

Premium Page Blobs

Premium high-performance page blob scenario

Note: All storage accounts are encrypted using SSE (Storage Service Encryption) for data at rest. 

Thank you !! Example HTML page Pleaes provide your valuable feedback.
Labels:

Comments

Post a Comment

Popular posts from this blog

Docker In Details

  Course Contents:- 1. Overview of Docker 2. Difference between Virtualization & Containerization 3. Installation & Configuration of Docker Runtime on Linux & Windows 4. Practice on Docker commands 5. launch a Webserver in a container 6. Launch public & official images of application like Jenkins, Nginx, DB etc.. 7. Launch a base OS Container 8. How to save changes inside the container & create a fresh image(commit) 9. How to ship image & container from one hardware to another. 10. How to remove stop/rm multiple container/images 11. Docker Registry 12. Docker Networking       Check current docker network                  Docker Network Bridge                     Docker Network Weaving                  Launch our own Docker Cluster with our defined Network             ...
Post a Comment
Read more

Jenkins

Pre-requisites 1. Install a Webserver https://gitlab.com/Azam-devops/webserver/-/blob/main/README.md Code for index.html https://gitlab.com/Azam-devops/webserver 2. Maven Code https://gitlab.com/Azam-devops/imperial-maven-project 1. Install & configure Jenkins Automation Server on Linux Vm. 2. Go through at some of the important options in Jenkins. 3. Manage Jenkins. 4. Plugins 5. Global Tools Configuration. 6. Credentials 7. Users 8. Slave Nodes 9. Configuring CI pipeline using Gitlab. 10. Configuring standalone CICD pipeline using. 11. Automating the CICD pipeline. 12. Jenkins log 13. Introduction to Jenkins file. 14. Basic groovy syntax & file formation. 15. Launching a Pipeline using Jenkins file. 3. DevOps Architecture Description of above DevOps plan. Create Maven based source code in Gitlab. Create a Jenkins job which will execute below stages. Checkout code from Gitlab Build/compile the source code using Maven as a build tool. scan the code virtually. Test...
Post a Comment
Read more

Roadmap to DevOps

    DevOps is nothing but the combination of process and philosophies which contains four basic component culture, collaboration, tools, and practices. In return, this gives a good automated system and infrastructure which helps an organisation to deliver a quality and reliable build. The beauty of this culture is it enables a quality for organizations to better serve their customers and compete more effectively in the market and also add some promised benefits which include confidence and trust, faster software releases, ability to solve critical issues quickly, and better manage unplanned work.   1. What are the tasks of a DevOps Engineer? Design, build, test and deploy scalable, distributed systems from development through production Manage the code repository(such as Git, SVN, BitBucket, etc.) including code merging and integrating, branching and maintenance and remote repository management Manage, configure and maintain infra...
Post a Comment
Read more

Git

Git Git  has steadily risen from being just a preferred skill to a must-have skill in last few years. in this blog we will go through top 20 git commands that every devops uses daily. If you don't have a gitlab account. please follow below link to create it free.   https://gitlab.com/ before using git please install git on your linux machine using below command. yum install git -y Use below command to create ssh keyol ssh-keygen -t rsa Below are the git command which we will cover in this blog. ·          git config ·          git init ·          git clone ·          git add ·          git commit ·          git diff ·          git reset ·      ...
2 comments
Read more

Ansible

  Ansible is an open-source software provisioning, configuration management, and application-deployment tool. It runs on many Unix-like systems, and can configure both Unix-like systems as well as Microsoft Windows. It includes its own declarative language to describe system configuration. Ansible was written by Michael DeHaan and acquired by Red Hat in 2015. Ansible is agentless, temporarily connecting remotely via SSH or Windows Remote Management (allowing remote PowerShell execution) to do its tasks. Platform support Control machines have to be a Linux/Unix host (for example SUSE Linux Enterprise, Red Hat Enterprise Linux, Debian, CentOS, macOS, BSD, Ubuntu, and Python 2.7 or 3.5 is required. Managed nodes, if they are Unix-like, must have Python 2.4 or later. For managed nodes with Python 2.5 or earlier, the python-simplejson package is also required. Since version 1.7, Ansible can also manage Windows nodes. In this case, native PowerShell remoting supported by the WS-Managemen...
Post a Comment
Read more