...

Azure store is Microsoft's cloud storage solution for modern data storage scenarios. Core storage services offer a massively scalable objects store for data objects, disk storage for Azure virtual machines, a file system service for the cloud, a messaging store for Reliable messaging, and in NOSQL stone. Azure blob storage is an object storage solution that you can use to store massive amounts of unstructured data such as text or binary data. Blob storage is ideal for serving images or documents directly to a browser, storing Data for archives are distributed, access streaming video, and audio and Disaster Recovery. Scenarios.

Azure file storage offers fully managed file shares in the cloud. And shares are accessible using industry standard Network Protocols mounting Azure file shares is just like an connecting to shares on your local network. Azure disk storage provides disks for virtual machines and applications, to access and use as they needed; similar to how they would access disks that were on premises.

Azure offers both solid state drives for higher performance workloads, and conventional hard drives for your less critical business scenarios. Azure Table Storage offers a NOSQL data store for key value pairs, using large-scale data sets. You can use as your table storage to store petabytes of semi-structured data and keep your costs down. Azure queue storage provides asynchronous message queuing for communication between application components, whether they are running in the cloud, on the desktop, on premises, or on mobile devices.

There are three Azure storage tiers that you can use to balance your costs: hot, cool and archive. The hot storage tier is optimized for storing data that is accessed frequently such as images for your website. The cool storage tier is optimized for data that is in frequently accessed and stored for at least 30 days, such as customer invoices. And the archive storage tier is appropriate for data that is rarely accessed and store for it is 180 days such as long-term backups.

Regardless of your business scenario, Azure has a solution to help you manage your storage needs.

In this video, we will discuss what we mean by Serverless Computing. Let's begin.

So as a software developer, you want to spend time doing what matters: building your application. You don't want to spend your time executing tedious time-consuming tasks, like installing an operating system or downloading system updates. The goal of serverless computing is to help you with this by taking care of those tiresome types of server management tasks, so that you can focus your efforts on getting your application to your customers.

So, that said, Serverless Computing is a bit of a misleading name because there are in fact servers being used. But what it really means is that the responsibility of managing servers is already handled for you. So in other words, it's an abstraction of servers so that you can take your mind off of infrastructure concerns and focus them on developer concerns.

There are three big benefits of using the serverless approach. First, there's no infrastructure management. So, that's, that's the first big one. And as a business, this means that you don't have to focus on administrative tasks like installing an operating system. Instead, you simply deploy your code and it automatically runs with high availability.

The second benefit is scalability. And as your application grows in popularity, you can rest assured that no matter what your application will continue working under any workload. In fact, Serverless Compute can scale from nothing to tens of thousands of requests, without any configuration.

Finally, the third benefit we want to point out is that you only pay for what you use. You see, Serverless Computing is event driven and that means that resources are only allocated from a direct action. So you are only charged for time it takes to run your code instead of paying for resources if they're not being used. And when all is said and done; time is money in the business world and, as such, you want to be focusing your time on what matters.

Using Azure to support Serverless Computing, through products like Azure functions, your main job will simply be to upload your code and you'll automatically get the benefits of infrastructure management and scalability, plus a payment model that will only charge you for what you use.

What is the microservice? In this video we'll talk about what microservices are and what they do. Okay, let's jump in. A microservice is just a web service that has a small well-defined scope and is loosely coupled from any other web service. Usually you don't build just one microservice but rather your organization adopts a microservices architecture that consists of a collection of microservices, each one self-contained and implementing a single business capability.

Each service has a separate codebase, which can be managed by a small development team. In fact microservices don't even need to share the same technology stack, libraries, or frameworks; which allows each team to choose the right tool for the job. This means that a single development team can build, test, and deploy a service. The result is a continuous innovation and a faster release cadence. Teams can now focus on one service and with a smaller scope of each service, the codebase will be easier to understand; making it easier for new team members to ramp up and to get started. Go this route, ow allows each microservice to be deployed independently, every other microservice in the organization.

It's you can update an existing service without rebuilding and redeploying the entire application. Plus. They can also easily roll back or roll forward and update if something goes wrong. The best part; his makes bug fixes and feature releases more manageable and less risky. The deployment strategy also means that each microservice can be scaled independently. A benefit of this efficiency is that each microservice is responsible for persisting its own data, or external state, and not rely on some common repository layer. In fact, some microservice experts insist that each microservice should even have its own separate database.

Again, the idea here is to make each microservice completely autonomous with no cross dependencies from the business domain perspective. This kind of freedom provides a layer of fault isolation. If a service goes down, it won't necessarily take out the entire application. Okay, great. But you might be thinking each microservice is an island unto itself. Then what happens when you need to work with multiple microservices in a single application? Good question. So here's the answer. Microservices can communicate with each other, by using well-defined apis. The internal implementation details in each service are encapsulated behind their interface. However, typically you'd want to reduce those interdependencies and try to introduce an orchestration or management layer in the higher-level consuming application that coordinates calls to various lower level microservices and combined results.

A microservices architecture solve some problems and is more appropriate when you have a large application that requires a high release velocity, you have complex applications that need to be highly scalable, you have applications with rich domains or many subdomains, You have an organization that consists of small development teams. Microservices can benefit from the management and hosting capabilities of several different Azure services. We'll talk about those in other modules.

But for now just do the microservices is a way to simplify an application architecture by focusing on creating smaller, more manageable, autonomous and independently deployable services, that address a single business domain or capability.

What is Kubernetes? As you may have noticed using containers to host applications and other processes has gone mainstream. As more, and more workflow is moved into containers management systems are needed to handle the demands of containerized applications at scale. One of the most popular options for managing container based workflow is Kubernetes. What is Kubernetes? Well, it combines container management automation with an extensible API to create a cloud native, application management Powerhouse.

At its core, Kubernetes manages the placement of pods which can consist of one or more containers on a Kubernetes cluster node. Additionally, if one of these pods crashes, Kubernetes can create a new instance other if a cluster node is removed Kubernetes can move any affected workload to a different node in the cluster. On top of that, Kubernetes pods can be scaled to provide more or less throughput to meet scale demands. And these scale operations can be triggered manually or automatically using Kubernetes horizontal pod Auto-scaling. Finally, if an application needs to be updated, Kubernetes can stagger the update deployment to minimize downtime. Plus if the update is problematic Kubernetes can roll back to a previous version.

Along with pd management, Kubernetes can also manage container storage and networking. Kubernetes persistent volumes can be used to persis data storage to one or more containers. This configuration allows containers to read and write application data and persist this data across many pod instances. That said, it is also common for an application running in Kubernetes to use cloud based storage and data systems such as a Azure storage or Azure Cosmos DB for data storage and retrieval.

In regard to networking, Kubernetes Network plugins provide capabilities such as exposing prods to the internet, load balancing traffic across multiple replicas of a pod, Network isolation and policy-driven network security. These networking plugins also manage communication and name resolution between pods in the Kubernetes cluster. The capabilities of Kubernetes are not limited to the built-in features additional capabilities can be created using a variety of methods for extending the Kubernetes API. With this flexibility operators can be created to perform custom actions such as producing Cloud events on pod creation, providing custom pod scheduling logic, and on-demand provisioning of managed cloud services, just to name a few The extension capabilities of Kubernetes, make it a great platform on which to build size services. So, we're hoping that this introduction gives you a solid understanding of using Kubernetes on Azure and that, you're now able to envision some opportunities for using it to accelerate and improve your own business operations.

In this video, we'll discuss the difference between virtual machines and containers. So let's begin.

Deploying server applications has always been complicated. That complexity drove system admins to start looking at virtualization techniques like virtual machines and containers. Virtual machines or VMs provide an abstraction layer for CPU memory and storage. Thet can be changed without having to invest in new hardware while still allowing the environment to be flexible and secure.

With VMs, you're in control, you decide the operating system, installed tools, and packages and your app runs either in isolation or with the other apps you install into the VM. But there are downsides. VMs can only run one operating system at a time. So if you have multiple server apps that all require different runtime environments, they may also require multiple virtual machines to execute properly, and because the be VM is emulating a full computer, tasks like starting one up, or taking a snapshot are pretty slow often taking several minutes.

But there's a lighter weight solution that solves some of these issues containers, A container bundles a single app and it's dependencies referred to as containerizing the app it then deploys it as a unit to a container host. The container host provides a standardized runtime environment, which abstracts away the operating system and infrastructure requirements, allowing the containerized application to run side by side with other containerized apps.

An easy way to differentiate between bands and containers is: virtual machines virtualize the hardware while containers virtualize the operating system. The operating system-level virtualization of containers is one reason why the container approach is more efficient than a full virtual machine. It allows you to run multiple lightweight containers on a single host, without sacrificing the isolation that the virtual machine originally offered. Azure your supports several container variations, the most popular being docker.

I'm like VMs, you can spin up containers quickly. You're just waiting for the app to launch instead of both the operating system and the app. Also containerized apps tend to be much smaller in size and the development process is simplified because your development runtime environment can look exactly like the production environment. Another advantage to containers is that they can be orchestrated with container cluster orchestration. You can easily deploy and manage multiple containerized applications without worrying about which server will host each container.

The decision of whether to use a VM or container, depends on how much flexibility you need. If you need to completely control the environment, then you might choose a VM. If not, then the portability, performance characteristics, and management capabilities of containers, might be the better choice.

Microsoft Azure has such an extensive array of services and features, how can you wrap your head around them all. We'll try to help you here, by breaking them down into ten main categories.

Compute These cloud services let you scale your computing capability on demand while only paying for what you use, add virtual machines as needed or scale your company's app services for web and mobile apps.

Networking these features that you connect your cloud and on-premise infrastructure in order to bring the best possible experience to your customers. VPNs and load balancing are just two examples of these features.

Storage Whether it's disk, file, blob, or archival storage; these services let you scale your data and app storage needs in a secure fashion.

Mobile With the mobile services, you can build and deploy a cross-platform in need of apps for any mobile device. Send notifications, you xamarin to build cloud-powered apps and take advantage of cognitive services to make your apps smarter.

Databases Choose from a variety of proprietary and open source database engines to bring your current databases to the cloud. Use tools to manage your SQL, Cosmos Db, MySQL and other data services.

Web These Services help you build deploy manage and scale your web applications. Create web apps published apis to your services or use Azure maps to provide geo-spatial context to your data.

Internet of Things Use these features to connect Monitor and manage all of your iot assets. Analyze the data, as it arrives from sensors, and then, take meaningful action with it.

Big data When you have large volumes of data, these open source cluster services will help you run analytics at a massive scale and make decisions based off of complex queries.

AI Use your existing data to forecast, future behaviors. Based on these AI services, use machine learning to build train and deploy models to the cloud.

DevOps DevOps brings together. People processes and Technology, by automating software delivery to provide continuous value to your users. with Azure DevOps, you can create build and release pipelines that provide continuous integration delivery and deployment for your applications.

These categories represent just a small fraction of what is available on Azure. Fortunately. It's easy to try out a new service then mix and match them to get exactly what you need. And the best part is you only pay for what you use.

The Azure portal is your one-stop graphical management solution for creating, configuring, and controlling all your Azure services and subscriptions. The portal makes it easy to create resources through a wizard-like environment From something as simple as to geographically redundant data base to a full Kubernetes cluster.

Once you have resources created, the portal lets you adjust the various parameters and settings for your resources, add users to your cloud-based active directory, implement security policies and plan backup schedules.

You can personalize your portal experience through custom dashboards, that you create to see the data that is most important to you. Within the portal, you can start and stop Services as needed.

You can scale your services by adding or removing resources from your subscription according to your business needs. You can also monitor the health of your applications, check your costs and billing status, analyze the performance of your applications in real time, or create reports for in-depth analysis. The Azure portal is your gateway to managing everything in your Azure subscription, whether you are creating new resources, configuring existing resources, or controlling Azure services.

The Azure portal is your place to manage your company's business on Azure.

Microsoft Azure is a private and public cloud platform that helps developers and IT administrators to build deploy and manage their applications.

Azure uses a technology known as Virtualization. Virtualization separates the tight coupling between a computer's hardware and its operating system using an abstraction layer called a Hypervisor. The Hypervisor emulates all the functions of a real computer and CPU and a virtual machine, optimizing the capacity of the abstracted Hardware. It can run multiple virtual machines at the same time and each virtual machine can run any compatible operating system, Such as Windows or Linux. Azure takes this virtualization technology and repeats it on a massive scale in Microsoft data centers throughout the world.

Each data center has many racks filled with servers and each server includes a Hypervisor to run multiple virtual machines. A network switch provides connectivity to all those servers. One server in each rack runs a special piece of software called a Fabric Controller. Each Fabric Controller is connected to another special piece of software known as the Orchestrator.

The Orchestrator is responsible for managing everything that happens in Azure including responding to user requests.

Users make requests using the Orchestrator's web API. The web API can be called by many tools, including the user interface of the Azure portal.

So, when a user makes a request to create a virtual machine, the Orchestrator packages everything that's needed, picks the best server rack, and then sends the packaging request to the Fabric Controller. Once the Fabric Controller has created the virtual machine, the user can connect to it. Azure makes it easy for developers and it administrators to be agile when they build deploy and manage their applications and services.

In fact, building a virtual machine is just the beginning of Azure's, ever-expanding, set of cloud services that will help you meet your business challenges. It gives you the freedom to build deploy and manage applications on a massive global network using your favorite tools and frameworks.

What is that Computing? Just like when you shop for your own computer, cloud computing lets you choose the power and features you need to run your software. What the difference is with cloud computing. The PC is in a cloud providers Data Center instead physically with you.

This lets you pay for only the services you use, plus someone else gets to manage the upkeep of the computer. Each cloud provider will have their own selection of services to choose from. But the basic services provided by all Cloud providers are Compute Power and Storage.

Compute power is how much processing your computer can do. For example, when buying a home computer, you may choose a computer with 8 gigabytes of RAM and the latest processor to run the software you need today, but as the load on the computer grows, you find that it slows down. With cloud computing, you can add or remove compute power as you need it.

This saves in cost since you only pay for the resources you use.

Storage is the volume of data you can store on your computer. A traditional computer has limited hard drive space. Over time, you may have to run out and buy another hard drive to store more data. With cloud computing. You can request more storage as you need it. Cloud providers manage the upkeep of the computer, so you don't have to. They will make sure that there are backups, that the operating system is up to date, as well as making sure that everything is up and running 24 hours a day. So as your business grows and your computing needs change, you can quickly bring on new computing resources in a cost-effective way.

Hi, I'm Christina Warren, senior Cloud Advocate; and that means that I spend my days explaining cloud computing to people like you. And I'd like to welcome you to Azure fundamentals learning path. Now, within this learning path, you'll get to understand some of the core cloud computing Concepts and what some of the advantages of cloud computing are. And you'll also be introduced to the cloud service model. Now, this learning path will also introduce you to Microsoft cloud computing offering, which is Microsoft azure.

And it'll help you understand how it works, what it does and more importantly you'll get a chance to be Hands-On with Microsoft Azure learning how to deploy website on the platform.

And lastly, the learning path will take you through some of the terminology that surrounds cloud Computing. So you'll be hearing terms like IAAS. PAAS, serverless, elasticity. And finally, you'll get to understand what they all mean.

On completion of this learning path, you'll have a great foundational knowledge to build on for your cloud computing Journey.

So what is devops? Well, the funny thing about when you say what is devops? You ask 10 people that devops is you'll probably get 20 different answers, right? But at Microsoft, devops means something very specific to us. Devops is the union of people, process, and products to enable The Continuous delivery of value to our end users. And now notice I said that really, really carefully, right? And the reason why is because One of them that definition was created by my manager. So if I get that wrong... The other thing is because every word of that was designed very specifically. The key is we want to continuously deliver value for our end users and this is vital in today's world.

Is breadcrumbing an ethical response to being breadcrumbed. why would this noy simply normalize what a supervisor or employer breadcrumbs?!

tip to address beadcrumb symtom that may well tem from poor leadership skills. Use YOUR power.

transient

In fact, the formula uses the top-left cell