Fichas
Azure Core Resources
Fichas del conjunto (19)
- 1Main Services - VM's - Azure Container Instances - Azure App Service - Azure functions (or server less computing)VM's
- Software version of physical computers
- Provide IaaS that can be used in different ways
- can customize software - 2VM Scale Sets - Used to deploy and manage a set of identical VM's - Supports autoscale & makes it easier to build large scale servicesGood for............
- Total control over OS
- To run custom software
- To use custom hosting configurations - 3When to use...... - During testing & development; quick way to create diff OS & application configurations- When running applications in the cloud; handling fluctuations in demand
- When extending your datacenter to the cloud; SharePoint can run on Azure VM instead of running locally - 4- During Disaster Recovery; can create VM's for critical applications & then close down when primary datacenter becomes operational againLift & Shift
Move from a physical server to the cloud - 5VM Scale Sets - Load balance VM's - Can build large scale services for areas such as compute, big data & container workloads - Ex. uploading astronomy images for processingAzure Batch
- Large scale & high performance computing (HPC)
- starts pool of compute, installs app & staging data, runs jobs with as many tasks as have, identifies failures, requeues work, scales down as work completes - 6ACI or AKS VM's limited to single OS, these are good for running multiple instances of an application on a single host machine- Can run multiple containers on a single physical or virtual host.
- don't manage, designed to be created, scaled out & stopped dynamically
- respond on demand such as a crash
- most popular container engine Docker - 7ACI - fast & simple, no need to manage VM or run additional services - it's a PaaS, allows to upload containers which are run for youAKS
- ORCHESTRATION; automating, managing & interacting with large number of containers - 8Microservice Architecture - Break solutions into smaller, independent pieces - Ex. splitting website, container host front end, another host for back end & third for storageAzure App Service
- Can build & host web apps, background jobs, mobile back ends and RESTFUL API's in any programming language without managing infrastructure - 9- Automatic scaling & high availability - supports windows & linux - enables automated deployments from GitHub, DevOps or any Git repoPaaS; allows to focus on website & API logic while Azure handles infrastructure
- Good to host web orientated applications - 10App Service Plan - cost; determines how much hardware is devoted to host (e.g. dedicated or shared hardware)Types of app services
- Web apps; diff languages supported for hosting web apps. Choose Windows or Linux as host operating sytem - 11API apps; can build REST based web API's by using choice of langauge & framework. Consumed from any HTTP & HTTPS based clientWebJobs; Run a program or script in same context as web app, API or mobile app. Scheduled or by trigger.
Used to run background tasks as part of application logic - 12Mobile Apps; quickly build back end for iOS & android apps. Store data in cloud SQL database, authenticate customers against social media providers, send push notifications, execute custom back end logicAzure Functions
- Server less computing; scaling & performance handled automatically by Azure.
- Event driven, only billed for resources that are used - 13- Abstraction of servers; platform manages. Each execution can run on a diff compute instance. which is transparent to the code. Code is deployed runs with high availability- Event Driven Scale; function contains code & metadata for triggers & bindings. Platform automatically scales number of compute instances based on rate of incoming events.
- 14Triggers define how function is invoked Bindings - declarative way to connect to services from within the code- Microbilling; only pay for the time the code runs. E.g. getting one hit a day on a website & not having to pay annual rate for website hosting. Can be cost effective
- 15Azure has 2 implementations of serverless compute; 1. Azure Functions 2. Azure Logic Apps1. Azure Functions
- used when needing to perform work to an event (often REST), timer or message from another Azure service. Responds quickly - 16- Good when concerned about code & not infrastructure - Good for variable demand - Only charged for CPU time when functions run (diff. to VM's)Functions can be stateless & stateful
1. Stateless; (default), act as if being restarted everytime to an event
2. Stateful (durable functions); context passed through function to track prior activity - 17FLEXIBILITY; can manage scaling, run on virtual networks & completely isolate functionsAzure Logic Apps
Functions execute code, logic apps execute WORKFLOW. Built from blocks & automate business scenarios - 18- Starts when triggered or when new data meets specific criteria - Logic app engine creates logic app instance that runs actions in workflow- can build custom connectors & workflow steps without writing code
- Designed in visual designer to see workflow
- Ideal for business analysts - 19Windows Virtual Desktop