Introduction to Microsoft Azure Well Architected Framework in Italian - Session 1 of 6
Introduzione a Microsoft Azure Well Architected Framework in Italiano - Sessione 1 di 6
Modulo 1: introduzione, principi e concetti base
The Microsoft Well Architected Framework For Data AnalyticsStephanie Locke
With more than a decade of organizations running large data & analytics workloads in the cloud, Microsoft have extended their architecture framework to provide best practices and guidance for businesses. In this session, we’ll introduce the 'Well Architected Framework', go into detail about effective data architectures, and give you concrete next steps you can take whether you already have a cloud data architecture or are planning your first implementation.
The document discusses strategies for executing a large-scale migration to AWS. It outlines establishing a cloud enablement team and AWS landing zone to provide a secure, scalable multi-account environment. Application migration strategies discussed include discovery, determining the migration path, rehosting/lift and shift, and replatforming/lift and reshape. Specific migration tools and services mentioned include AWS Application Discovery Service, VMware HCX, AWS Server Migration Service, and AWS Database Migration Service.
Cloud Center of Excellence - DatasheetTodd Erskine
Cloud Center of Excellence (CCoE) provides a programmatic approach to implement, manage, and operate the Microsoft Azure platform for onboarding projects and Azure workloads effectively.
The document discusses the benefits of establishing a Cloud Center of Excellence (CCoE) for an organization. A CCoE can help standardize processes, establish best practices, and drive innovation around cloud adoption. It recommends that a CCoE have leadership teams to specialize in areas like infrastructure, security, and operations. A successful CCoE will also focus on automation, continuous integration and deployment, and selecting the right people who are results-oriented and customer-focused to help deliver wins for the organization. The CCoE framework allows for consistency, efficiency, and helps both IT teams and leadership realize the full benefits and potential of the cloud.
Cloud Migration, Application Modernization and Security for PartnersAmazon Web Services
As AWS continues to expand, enterprise customers are increasingly looking to our partner ecosystem to assist in migrating their workloads to the cloud. This session describes the challenges, lessons learned and best practices for large scale application migrations. We will use real examples from our consulting partners and AWS Professional Services to illustrate how to move workloads to the cloud while modernizing the associated applications to take advantage of AWS’ unique benefits. We will also dive into how to use an array of AWS services and features to improve a customer’s security posture as they are migrating and once they are up and running in the cloud.
Accelerate your Cloud Migration Journey (Level 100)
Many enterprises have realized the benefits of migrating services to the cloud and are considering the next stage in their journey. In this webinar we will take you through the principles of cloud migration including the business benefits, cloud economics, methodologies and tools to accelerate your journey. We will also discuss the key enablers for cloud adoption based on real examples.
This is a Level 100 webinar
Speakers: Manav Prabhakar, Practice Manager, AWS Professional Services
Jon Austin, Principal Solutions Architect, Amazon Web Services
Parijat Mishra, Solutions Architect Manager, Amazon Web Services
Introduction to the Well-Architected Framework and Tool - SVC208 - Anaheim AW...Amazon Web Services
Most modern businesses depend on a portfolio of technology solutions to operate and be successful every day. How do you know whether your team is following best practices or what the risks are in your architectures? This session shows how the AWS Well-Architected Framework provides prescriptive advice on best practices and how the AWS Well-Architected Tool enables you to measure and improve your technology portfolio. We explain how other customers are using AWS Well-Architected in their businesses, and we share what we learned from reviewing tens of thousands of architectures across operational excellence, security, reliability, performance efficiency, and cost optimization.
HUAWEI CLOUD General Introduction-for partner.pdfDanyMochtar
Huawei provides a full-stack cloud solution including infrastructure, platform and software services. It has built pre-integrated AI solutions for multiple industries. Huawei grows its ecosystem by sharing infrastructure and providing tools to help partners build solutions on its cloud platform. This allows customers to access a wide range of partner solutions through Huawei Cloud's marketplace.
The Microsoft Well Architected Framework For Data AnalyticsStephanie Locke
With more than a decade of organizations running large data & analytics workloads in the cloud, Microsoft have extended their architecture framework to provide best practices and guidance for businesses. In this session, we’ll introduce the 'Well Architected Framework', go into detail about effective data architectures, and give you concrete next steps you can take whether you already have a cloud data architecture or are planning your first implementation.
The document discusses strategies for executing a large-scale migration to AWS. It outlines establishing a cloud enablement team and AWS landing zone to provide a secure, scalable multi-account environment. Application migration strategies discussed include discovery, determining the migration path, rehosting/lift and shift, and replatforming/lift and reshape. Specific migration tools and services mentioned include AWS Application Discovery Service, VMware HCX, AWS Server Migration Service, and AWS Database Migration Service.
Cloud Center of Excellence - DatasheetTodd Erskine
Cloud Center of Excellence (CCoE) provides a programmatic approach to implement, manage, and operate the Microsoft Azure platform for onboarding projects and Azure workloads effectively.
The document discusses the benefits of establishing a Cloud Center of Excellence (CCoE) for an organization. A CCoE can help standardize processes, establish best practices, and drive innovation around cloud adoption. It recommends that a CCoE have leadership teams to specialize in areas like infrastructure, security, and operations. A successful CCoE will also focus on automation, continuous integration and deployment, and selecting the right people who are results-oriented and customer-focused to help deliver wins for the organization. The CCoE framework allows for consistency, efficiency, and helps both IT teams and leadership realize the full benefits and potential of the cloud.
Cloud Migration, Application Modernization and Security for PartnersAmazon Web Services
As AWS continues to expand, enterprise customers are increasingly looking to our partner ecosystem to assist in migrating their workloads to the cloud. This session describes the challenges, lessons learned and best practices for large scale application migrations. We will use real examples from our consulting partners and AWS Professional Services to illustrate how to move workloads to the cloud while modernizing the associated applications to take advantage of AWS’ unique benefits. We will also dive into how to use an array of AWS services and features to improve a customer’s security posture as they are migrating and once they are up and running in the cloud.
Accelerate your Cloud Migration Journey (Level 100)
Many enterprises have realized the benefits of migrating services to the cloud and are considering the next stage in their journey. In this webinar we will take you through the principles of cloud migration including the business benefits, cloud economics, methodologies and tools to accelerate your journey. We will also discuss the key enablers for cloud adoption based on real examples.
This is a Level 100 webinar
Speakers: Manav Prabhakar, Practice Manager, AWS Professional Services
Jon Austin, Principal Solutions Architect, Amazon Web Services
Parijat Mishra, Solutions Architect Manager, Amazon Web Services
Introduction to the Well-Architected Framework and Tool - SVC208 - Anaheim AW...Amazon Web Services
Most modern businesses depend on a portfolio of technology solutions to operate and be successful every day. How do you know whether your team is following best practices or what the risks are in your architectures? This session shows how the AWS Well-Architected Framework provides prescriptive advice on best practices and how the AWS Well-Architected Tool enables you to measure and improve your technology portfolio. We explain how other customers are using AWS Well-Architected in their businesses, and we share what we learned from reviewing tens of thousands of architectures across operational excellence, security, reliability, performance efficiency, and cost optimization.
HUAWEI CLOUD General Introduction-for partner.pdfDanyMochtar
Huawei provides a full-stack cloud solution including infrastructure, platform and software services. It has built pre-integrated AI solutions for multiple industries. Huawei grows its ecosystem by sharing infrastructure and providing tools to help partners build solutions on its cloud platform. This allows customers to access a wide range of partner solutions through Huawei Cloud's marketplace.
This document discusses best practices for creating a secure and optimized landing zone for migrating applications to AWS. It covers recommendations in key areas such as account structure, networking, identity and access management, and service catalog. The goal is to provide a standardized, automated environment where applications can be migrated and operated securely at scale. Specific strategies covered include using separate accounts for production/non-production workloads, implementing VPC designs with private subnets and Direct Connect, controlling access with IAM policies, and providing self-service access to approved services through the service catalog.
Reduce Costs and Build a Strong Operational Foundation with the AWS Migration...Amazon Web Services
Speaker: Romulo Gapuz, Solutions Architect, AWS
Up to 80% of enterprise IT budgets are spent on maintaining existing workloads and keeping the lights on versus focusing on new products and services to better serve customers. Migrating existing workloads to the cloud provide a lever to do that, providing efficiencies and benefits on your existing workloads.
What if you could focus your attention and resources on differentiating your company in the marketplace? What if you could innovate at startup-like speed? And finally, what if you could dramatically reduce the risks inherent in your present infrastructure?
Microsoft Cloud Adoption Framework for Azure: Governance ConversationNicholas Vossburg
This document outlines Microsoft's Cloud Adoption Framework (CAF) governance model for governing cloud adoption. It recommends starting with an assessment of the current state and future vision. Then establish a Minimum Viable Product (MVP) for governance using core Azure services like management groups, subscriptions, resource groups, Azure Policy and role-based access control. The MVP should focus on key areas like resource tagging, grouping and security baselines. Governance then evolves by maturing the MVP with each cloud release to better align with cloud adoption and IT functions.
Rodney Grilli from AWS Professional Services gave a webinar on large-scale AWS migrations. He covered the AWS Cloud Adoption Framework, considerations for large migration planning and execution, using a migration playbook and central migration portal. The portal includes knowledge management, asset management, help desk and reporting dashboard functions. It also features an automated migration playbook. Lessons learned focused on upfront planning, comprehensive discovery, transparency, proper project management and playbook automation.
AWS re:Invent 2016: Building Enterprise Cloud Operations As a Service with T-...Amazon Web Services
After launching several thousand EC2 instances in the cloud, we've learned that the key to running an IT fleet successfully on AWS is enforcing operational and economic discipline. As AWS service consumption grows, operational costs and overhead shouldn't grow linearly. Instead, IT should encourage new tenants that migrate from data centers to AWS to slowly shift toward a self-service delivery model and adopt the DevOps operations model. Creating and offering an AWS Cloud operations service catalog enables organizations to efficiently take full advantage of AWS' flexibility and modularity. T-Mobile, whose journey to AWS Cloud management started more than 2 years ago, uses a service catalog to enforce operational discipline in the Cloud. Their catalog is custom crafted for each Cloud-based IT workload. This session provides insight into the AWS Cloud operations strategy and its transformation, the creation of a Cloud operations service catalog, and how this approach supports reliable engineering on AWS. Sponsored by Accenture.
AWS Competency Partner
This document provides an overview of Azure Boards and its key features for tracking work, managing backlogs and sprints, running queries, and viewing dashboards. Azure Boards allows teams to track work using Kanban boards, backlogs, and dashboards. It enables tracking work from idea to release with all code changes linked to work items. Teams can also use built-in tools to help run scrum processes. The tool provides insights into project health using analytics and widgets.
How can you accelerate the delivery of new, high-quality services? How can you be able to experiment and get feedback quickly from your customers? To get the most out of the agility afforded by serverless and containers, it is essential to build CI/CD pipelines that help teams iterate on code and quickly release features. In this talk, we demonstrate how developers can build effective CI/CD release workflows to manage their serverless or containerized deployments on AWS. We cover infrastructure-as-code (IaC) application models, such as AWS Serverless Application Model (AWS SAM) and new imperative IaC tools. We also demonstrate how to set up CI/CD release pipelines with AWS CodePipeline and AWS CodeBuild, and we show you how to automate safer deployments with AWS CodeDeploy.
(ENT206) Migrating Thousands of Workloads to AWS at Enterprise Scale | AWS re...Amazon Web Services
Migrating workloads to AWS in an enterprise environment is not easy, but with the right approach, an enterprise-sized organization can migrate thousands of instances to AWS quickly and cost effectively. You can leave this session with a good understanding of the migration framework used to assess an enterprise application portfolio and how to move thousands of instances to AWS in a quick and repeatable fashion.
In this session, we describe the components of Accenture's cloud migration framework, including tools and capabilities provided by Accenture, AWS, and third-party software solutions, and how enterprises can leverage these techniques to migrate efficiently and effectively. The migration framework covers:
- Defining an overall cloud strategy
- Assessing the business requirements, including application and data requirements
- Creating the right AWS architecture and environment
- Moving applications and data using automated migration tools- Services to manage the migrated environment
This document provides an overview of migrating on-premises workloads to Azure using Azure Migrate. It discusses the benefits of moving to the cloud, such as cost savings, increased agility and new capabilities. It also covers Azure Migrate features for discovering, assessing and migrating virtual machines, databases, app services and containers to Azure. Specific migration strategies and phases are outlined. Demo screenshots showcase assessing and migrating VMs and databases with Azure Migrate tools.
Discover the benefits of migrating mainframe environments to AWS and the best practices learned by helping customers modernize mainframes through IT transformation strategy and planning. Learn about running mainframe software in the AWS Cloud, including different approaches, benefits of modernization, how to deal with legacy code, and more.
This document provides an overview of modernizing enterprise applications with Azure Platform-as-a-Service (PaaS). It discusses reasons why businesses modernize like reducing technical debt and optimizing costs. It also covers challenges of modernization like fragmented security and conflicting priorities. The document then presents different approaches to application migration and modernization on Azure including migrating to IaaS, replacing with SaaS, staying on-premises but connected to cloud, and modernizing directly on PaaS. Key benefits of a successful modernization are also listed like prioritizing security, resilience, and performance as well as innovating faster. The document concludes with case studies of companies successfully modernizing applications on Azure.
This document provides an overview of the Microsoft Cloud Adoption Framework for Azure. It begins by explaining why cloud adoption is important, noting that 91% of organizations see digital transformation as critical to their business and that shifting to the cloud can provide significant cost savings and revenue benefits. It then introduces the Cloud Adoption Framework, which is an iterative process to help organizations define their cloud strategy, plan their adoption, prepare for change, adopt technologies by migrating or innovating, and govern and manage their cloud environment. Common blockers to cloud adoption are discussed along with the various tools, templates, and assessments available to help organizations overcome those blockers at each stage of the framework.
In this session, we cover all options for running containers on AWS. This includes an introduction of container concepts and an overview of the different services: Amazon Elastic Container Service, AWS Fargate, and Amazon Elastic Container Service for Kubernetes. We also cover best practices for how to choose the right orchestration platform for your workload, the different tools for making this process easier, and ways to find more information and support as you work.
As enterprises build their cloud adoption strategy, conducting a cloud readiness assessment is of strategic importance. HCL believes that application readiness and compliance controls are the pre-requisites for determining a business-oriented cloud adoption strategy.
HCL’s Cloud Assessment and Readiness Tool (CART) enable organizations to assess their “Cloud-readiness” using a powerful self-driven analysis. It uses a broad array of 25 technical, business, compliances and security parameters to perform the cloud-readiness analysis across three different aspects - Technical & Architecture, Application & Security. The Tool is based on Excel based workbook with easy to use methodology for filling the data & then helps generating a standard & basic Cloud Assessment within minutes
클라우드의 전개 유형별 특징을 살펴보고 클라우드로 전환하기 위해 고려해야 할 사항과 실제 사례를 공유합니다.
목차
1. 클라우드 세상
2. 클라우드 유형
3. 클라우드 도입 전략
4. 고객 사례
5. 요약
대상
- 클라우드에 관심이 있는 분
- 클라우드 전환을 고려하시는 분
- 잠깐 휴식을 취하고 싶은 개발자
Azure Arc allows organizations to manage and deploy Azure services across any infrastructure including multicloud and edge locations. It provides a single control plane to operate hybrid resources as native Azure resources. The presentation discusses Azure Arc-enabled infrastructure, services, security capabilities and how Azure Arc can be deployed on AIS Cloud X to help local enterprises gain central visibility and operations while building cloud native applications anywhere.
This document provides a guide for migrating infrastructure, databases, and applications to the cloud. It discusses why organizations are choosing to migrate now, including reducing costs, increasing flexibility and scalability, and improving security. The guide outlines Microsoft's Cloud Adoption Framework for planning and executing a cloud migration. It covers strategies for assessing the current environment, planning the migration, moving workloads to the cloud, and ongoing management after migration. The goal is to provide best practices to help organizations efficiently and successfully migrate to the cloud.
Azure Cloud Adoption Framework + Governance - Sana Khan and Jay Kumar Timothy McAliley
The document discusses Microsoft's Cloud Adoption Framework for Azure, which provides guidance to help organizations adopt cloud technologies in a controlled and stable manner while also enabling innovation and growth. The framework is modular and covers key areas of Ready, Plan, Adopt, and Govern to help align business and technology strategies. It provides best practices and blueprints for building cloud foundations, migrating workloads, modernizing applications, and establishing governance policies to manage cloud operations and ensure compliance. The goal is to help customers achieve a balance of control, stability, speed and results in their cloud adoption journey.
Introduction to Microsoft Azure Well Architected Framework in Italian - Session 5 of 6
Introduzione a Microsoft Azure Well Architected Framework in Italiano - Sessione 5 di 6
Modulo 5: eccellenza operativa
Introduction to Microsoft Azure Well Architected Framework in Italian - Session 2 of 6
Introduzione a Microsoft Azure Well Architected Framework in Italiano - Sessione 2 di 6
Modulo 2: affidabilità
This document discusses best practices for creating a secure and optimized landing zone for migrating applications to AWS. It covers recommendations in key areas such as account structure, networking, identity and access management, and service catalog. The goal is to provide a standardized, automated environment where applications can be migrated and operated securely at scale. Specific strategies covered include using separate accounts for production/non-production workloads, implementing VPC designs with private subnets and Direct Connect, controlling access with IAM policies, and providing self-service access to approved services through the service catalog.
Reduce Costs and Build a Strong Operational Foundation with the AWS Migration...Amazon Web Services
Speaker: Romulo Gapuz, Solutions Architect, AWS
Up to 80% of enterprise IT budgets are spent on maintaining existing workloads and keeping the lights on versus focusing on new products and services to better serve customers. Migrating existing workloads to the cloud provide a lever to do that, providing efficiencies and benefits on your existing workloads.
What if you could focus your attention and resources on differentiating your company in the marketplace? What if you could innovate at startup-like speed? And finally, what if you could dramatically reduce the risks inherent in your present infrastructure?
Microsoft Cloud Adoption Framework for Azure: Governance ConversationNicholas Vossburg
This document outlines Microsoft's Cloud Adoption Framework (CAF) governance model for governing cloud adoption. It recommends starting with an assessment of the current state and future vision. Then establish a Minimum Viable Product (MVP) for governance using core Azure services like management groups, subscriptions, resource groups, Azure Policy and role-based access control. The MVP should focus on key areas like resource tagging, grouping and security baselines. Governance then evolves by maturing the MVP with each cloud release to better align with cloud adoption and IT functions.
Rodney Grilli from AWS Professional Services gave a webinar on large-scale AWS migrations. He covered the AWS Cloud Adoption Framework, considerations for large migration planning and execution, using a migration playbook and central migration portal. The portal includes knowledge management, asset management, help desk and reporting dashboard functions. It also features an automated migration playbook. Lessons learned focused on upfront planning, comprehensive discovery, transparency, proper project management and playbook automation.
AWS re:Invent 2016: Building Enterprise Cloud Operations As a Service with T-...Amazon Web Services
After launching several thousand EC2 instances in the cloud, we've learned that the key to running an IT fleet successfully on AWS is enforcing operational and economic discipline. As AWS service consumption grows, operational costs and overhead shouldn't grow linearly. Instead, IT should encourage new tenants that migrate from data centers to AWS to slowly shift toward a self-service delivery model and adopt the DevOps operations model. Creating and offering an AWS Cloud operations service catalog enables organizations to efficiently take full advantage of AWS' flexibility and modularity. T-Mobile, whose journey to AWS Cloud management started more than 2 years ago, uses a service catalog to enforce operational discipline in the Cloud. Their catalog is custom crafted for each Cloud-based IT workload. This session provides insight into the AWS Cloud operations strategy and its transformation, the creation of a Cloud operations service catalog, and how this approach supports reliable engineering on AWS. Sponsored by Accenture.
AWS Competency Partner
This document provides an overview of Azure Boards and its key features for tracking work, managing backlogs and sprints, running queries, and viewing dashboards. Azure Boards allows teams to track work using Kanban boards, backlogs, and dashboards. It enables tracking work from idea to release with all code changes linked to work items. Teams can also use built-in tools to help run scrum processes. The tool provides insights into project health using analytics and widgets.
How can you accelerate the delivery of new, high-quality services? How can you be able to experiment and get feedback quickly from your customers? To get the most out of the agility afforded by serverless and containers, it is essential to build CI/CD pipelines that help teams iterate on code and quickly release features. In this talk, we demonstrate how developers can build effective CI/CD release workflows to manage their serverless or containerized deployments on AWS. We cover infrastructure-as-code (IaC) application models, such as AWS Serverless Application Model (AWS SAM) and new imperative IaC tools. We also demonstrate how to set up CI/CD release pipelines with AWS CodePipeline and AWS CodeBuild, and we show you how to automate safer deployments with AWS CodeDeploy.
(ENT206) Migrating Thousands of Workloads to AWS at Enterprise Scale | AWS re...Amazon Web Services
Migrating workloads to AWS in an enterprise environment is not easy, but with the right approach, an enterprise-sized organization can migrate thousands of instances to AWS quickly and cost effectively. You can leave this session with a good understanding of the migration framework used to assess an enterprise application portfolio and how to move thousands of instances to AWS in a quick and repeatable fashion.
In this session, we describe the components of Accenture's cloud migration framework, including tools and capabilities provided by Accenture, AWS, and third-party software solutions, and how enterprises can leverage these techniques to migrate efficiently and effectively. The migration framework covers:
- Defining an overall cloud strategy
- Assessing the business requirements, including application and data requirements
- Creating the right AWS architecture and environment
- Moving applications and data using automated migration tools- Services to manage the migrated environment
This document provides an overview of migrating on-premises workloads to Azure using Azure Migrate. It discusses the benefits of moving to the cloud, such as cost savings, increased agility and new capabilities. It also covers Azure Migrate features for discovering, assessing and migrating virtual machines, databases, app services and containers to Azure. Specific migration strategies and phases are outlined. Demo screenshots showcase assessing and migrating VMs and databases with Azure Migrate tools.
Discover the benefits of migrating mainframe environments to AWS and the best practices learned by helping customers modernize mainframes through IT transformation strategy and planning. Learn about running mainframe software in the AWS Cloud, including different approaches, benefits of modernization, how to deal with legacy code, and more.
This document provides an overview of modernizing enterprise applications with Azure Platform-as-a-Service (PaaS). It discusses reasons why businesses modernize like reducing technical debt and optimizing costs. It also covers challenges of modernization like fragmented security and conflicting priorities. The document then presents different approaches to application migration and modernization on Azure including migrating to IaaS, replacing with SaaS, staying on-premises but connected to cloud, and modernizing directly on PaaS. Key benefits of a successful modernization are also listed like prioritizing security, resilience, and performance as well as innovating faster. The document concludes with case studies of companies successfully modernizing applications on Azure.
This document provides an overview of the Microsoft Cloud Adoption Framework for Azure. It begins by explaining why cloud adoption is important, noting that 91% of organizations see digital transformation as critical to their business and that shifting to the cloud can provide significant cost savings and revenue benefits. It then introduces the Cloud Adoption Framework, which is an iterative process to help organizations define their cloud strategy, plan their adoption, prepare for change, adopt technologies by migrating or innovating, and govern and manage their cloud environment. Common blockers to cloud adoption are discussed along with the various tools, templates, and assessments available to help organizations overcome those blockers at each stage of the framework.
In this session, we cover all options for running containers on AWS. This includes an introduction of container concepts and an overview of the different services: Amazon Elastic Container Service, AWS Fargate, and Amazon Elastic Container Service for Kubernetes. We also cover best practices for how to choose the right orchestration platform for your workload, the different tools for making this process easier, and ways to find more information and support as you work.
As enterprises build their cloud adoption strategy, conducting a cloud readiness assessment is of strategic importance. HCL believes that application readiness and compliance controls are the pre-requisites for determining a business-oriented cloud adoption strategy.
HCL’s Cloud Assessment and Readiness Tool (CART) enable organizations to assess their “Cloud-readiness” using a powerful self-driven analysis. It uses a broad array of 25 technical, business, compliances and security parameters to perform the cloud-readiness analysis across three different aspects - Technical & Architecture, Application & Security. The Tool is based on Excel based workbook with easy to use methodology for filling the data & then helps generating a standard & basic Cloud Assessment within minutes
클라우드의 전개 유형별 특징을 살펴보고 클라우드로 전환하기 위해 고려해야 할 사항과 실제 사례를 공유합니다.
목차
1. 클라우드 세상
2. 클라우드 유형
3. 클라우드 도입 전략
4. 고객 사례
5. 요약
대상
- 클라우드에 관심이 있는 분
- 클라우드 전환을 고려하시는 분
- 잠깐 휴식을 취하고 싶은 개발자
Azure Arc allows organizations to manage and deploy Azure services across any infrastructure including multicloud and edge locations. It provides a single control plane to operate hybrid resources as native Azure resources. The presentation discusses Azure Arc-enabled infrastructure, services, security capabilities and how Azure Arc can be deployed on AIS Cloud X to help local enterprises gain central visibility and operations while building cloud native applications anywhere.
This document provides a guide for migrating infrastructure, databases, and applications to the cloud. It discusses why organizations are choosing to migrate now, including reducing costs, increasing flexibility and scalability, and improving security. The guide outlines Microsoft's Cloud Adoption Framework for planning and executing a cloud migration. It covers strategies for assessing the current environment, planning the migration, moving workloads to the cloud, and ongoing management after migration. The goal is to provide best practices to help organizations efficiently and successfully migrate to the cloud.
Azure Cloud Adoption Framework + Governance - Sana Khan and Jay Kumar Timothy McAliley
The document discusses Microsoft's Cloud Adoption Framework for Azure, which provides guidance to help organizations adopt cloud technologies in a controlled and stable manner while also enabling innovation and growth. The framework is modular and covers key areas of Ready, Plan, Adopt, and Govern to help align business and technology strategies. It provides best practices and blueprints for building cloud foundations, migrating workloads, modernizing applications, and establishing governance policies to manage cloud operations and ensure compliance. The goal is to help customers achieve a balance of control, stability, speed and results in their cloud adoption journey.
Introduction to Microsoft Azure Well Architected Framework in Italian - Session 5 of 6
Introduzione a Microsoft Azure Well Architected Framework in Italiano - Sessione 5 di 6
Modulo 5: eccellenza operativa
Introduction to Microsoft Azure Well Architected Framework in Italian - Session 2 of 6
Introduzione a Microsoft Azure Well Architected Framework in Italiano - Sessione 2 di 6
Modulo 2: affidabilità
Introduction to Microsoft Azure Well Architected Framework in Italian - Session 6 of 6
Introduzione a Microsoft Azure Well Architected Framework in Italiano - Sessione 6 di 6
Modulo 6: efficienza delle prestazioni
Building infrastructure as code with typescript and aws cdkAndrea Valentini
The AWS CDK is a software development framework to define cloud infrastructure as code and provision it through CloudFormation. The CDK integrates fully with AWS services and offers a higher-level object-oriented abstraction to define AWS resources imperatively. The CDK improves your end-to-end development experience because you get to use the power of modern programming languages to define your AWS infrastructure in a predictable and efficient manner.” You can build test and deploy a true Infrastructure as a Code architecture using Typescript. make Reusable code and enjoy the code completion feature of IDE’s to create your cloud Infrastructure.
OVERVIEW: Java secondo Microsoft
STRUMENTI:Java nel cloud
MODALITA’: Il Development life cycle secondo Microsoft
APPROCCIO: Stack cloud native basato su JAVA ed Azure
CAMBIAMENTO: Know how necessario per lo sviluppo su AZURE con Java
OPPORTUNITA: Use case di implementazione «first approach»
"Sistemi managed in alta affidabilità e in open source" by Andrea Di MarcoThinkOpen
13/02/2018
Il mondo del cloud computing: point of failure, sia a livello architetturale che fisico, dei servizi oggi presenti sul mercato, ma anche nuove possibili soluzioni per l'alta affidabilità.
Italian .NEXT on Tour Keynote and Technical SlidedeckNEXTtour
If you missed the sold-out Nutanix .NEXT Conference, register now to attend .NEXT On Tour and get a front row seat as we reveal Nutanix Acropolis and Prism - solutions that will power the next generation of enterprise computing.
Introduction to Microsoft Azure Well Architected Framework in Italian - Session 3 of 6
Introduzione a Microsoft Azure Well Architected Framework in Italiano - Sessione 3 di 6
Modulo 3: sicurezza
Anno Accademico 2015
2015-2016
corso di Economia e Organizzazione Aziendale
Ingegneria Informatica (Laurea Mag.) 2o Anno (Secondo S.)
LEZIONE INTRODUTTIVA – VERSO L’ECONOMIA
DIGITALE – I TEMI DELLA TRASFORMAZIONE
07 Marzo 2016 – dalle ore 8.30 alle 10.30
AULA C2A – DIETI
Presentazione: La prima lezione del corso di Economia e Organizzazione Aziendale per
Ingegneria Informatica (Laurea Mag.) 2o Anno (Secondo S.) introduce i temi della trasformazione
in atto per effetto dei cambiamenti delle tecnologie della comunicazione e dell’informazione (ICT) e
presenta possibili scenari dell’economia digitale. La lezione è in forma di evento aperto ed ospita
ma
gli interventi di soggetti che operano nel mercato sul fronte della trasformazione.
PROGRAMMA
08,30
08,40
09,00
09,20
09,40
10,00
10,20
Carlo Sansone Coordinatore del CdL in Ingegneria Informatica
L’Università e la trasformazione digitale
Luigi Bianco – responsabile FEDERMANAGER per l’AGENDA DIGITALE
Le sfide del Management per la trasformazione digitale
Marco Lombardo – INDUSTRIA ITALIANA DEL SOFTWARE LIBERO – “Didotech”
Gli Agenti del mercato dopo la TRASFORMAZIONE DIGITALE
Fabio Cecaro, Presidente EUROCLOUD Italy
Il CLOUD per le Piccole e Medie Imprese
Francesco Castagna – Amministratore Delegato di SMS Engineering
Domanda e offerta di servizi per la trasformazione digitale – agenda digitale aziendale
Bruno Esposito – FORUM della RESPONSABILITÀ SOCIALE IN CAMPANIA
La responsabilità digitale per un’economia sostenibile
Valerio Teta docente incaricato del corso
Introduction to Microsoft Azure Well Architected Framework in Italian - Session 4 of 6
Introduzione a Microsoft Azure Well Architected Framework in Italiano - Sessione 4 di 6
Modulo 4: ottimizzazione dei costi
Terraform and Infrastructure as Code (IaC): an introduction of the reason why this kind of solution had been created and an explanation of the concepts and usage, with a link in the notes to a demo project available in GitHub.
Kubernetes the deltatre way the basics - introduction to containers and orc...Rauno De Pasquale
The basics - Introduction to Containers and Orchestrators (May 18th, 2020)
by Rauno De Pasquale (Newesis), supported by Cristiano Degiorgis (Deltatre)
A new version of the introduction to containers and orchestrator, done for the series of events "Kubernetes - The Deltatre way".
Knowing the context and concepts behind container use is essential to be able to proceed on the path that will lead to master Kubernetes and Cloud Native applications. This initial session is about basic skills to answer questions such as: what is a container image? Why did anyone feel the need for an orchestrator? Are there any alternatives to Docker and Kubernetes? How does working with containers and Kubernetes connect to traditional virtualization? The session aims to provide the basic skills to be able to guide yourself in the next sessions where the ways of creating and execution of applications in Kubernetes environment will be tackled.
Recorded session: YouTube | Facebook
Repository: https://github.com/deltatrelabs/community-events-kubernetes-the-deltatre-way
DevOps Torino Meetup - DevOps Engineer, a role that does not exist but is muc...Rauno De Pasquale
The third appointment of the DevOps Meetup in Turin. We made a survey to collect data to discuss about the usage of the term "DevOps Engineer" to define a specific role. Is it really a role? And how this role compare with the ones of SysAdmin, Cloud Engineer, SRE or Developer? Which are the different organisation model used for each of these roles? Which are the skills and area of competences?
Independently from the DevOps movement but starting from the same problems, Google developed its own strategy defining a new specific role called SRE (Site Reliability Engineer). This introduction tries to explain the history and the concept of this methodology and to compare it with the DevOps manifesto to understand what does it mean to adopt DevOps and what does it mean to be an SRE and what the two things are sharing and where they diverge.
DevOps Torino Meetup Group Kickoff Meeting - Why a meetup group on DevOps, wh...Rauno De Pasquale
Torino DevOps Meetup Group - Culture, Processes and Tools.
There is a lot of talking about DevOps culture and practices with different point of views and a lot of misunderstandings. This group aims to create a point of discussion to share experience, analysis and thoughts to help each us to better understand and implement DevOps approaches into our way of working in the Digital Services.
Si parla molto di DevOps ma rimane molta confusione circa il significato del termine, ci sono molti punti di vista diversi e anche diversi fraintendimenti. Questo gruppo si prefigge lo scopo di diventare un punto di aggregazione per condividere esperienze, studi e pensieri circa la cultura e le pratiche DevOps per poter giungere insieme a una migliore comprensione che ci possa aiutare a portare questo approccio nel nostro lavoro in ambito IT.
This document provides an introduction to containers and container orchestration technologies. It discusses the evolution from virtual machines to containers and the benefits of containers. It then explains why an orchestrator tool is needed to manage containers at scale. The remainder of the document defines common container and orchestration concepts, including Docker, Kubernetes objects and components, Helm for package management, and Istio for traffic management and security.
The document provides an introduction to cloud computing, discussing key concepts, common mistakes, and Newesis' experience with cloud adoption. Specifically:
- It defines cloud computing as a new type of service with capabilities beyond remote hosting, and discusses new use cases enabled by different cloud technologies.
- It outlines common mistakes like assuming costs will always be higher, capacity is infinite, or that availability and security are handled automatically.
- It shares Newesis' journey working with various cloud vendors since 2009 and why they recommend a multi-cloud approach to avoid lock-in and select the best cloud for a given need.
- Finally, it presents Newesis' "Cloud Cookbook" approach of transforming systems for the
2. ABOUT ME
➤ Rauno De Pasquale, Co-Founder and CTO at Newesis Srl,
constantly trying to reconcile his degree in Philosophy with
a passion for computer science. After almost 18 year at
Deltatre, at the beginning of 2019 he creates Newesis, with
the aim of simplifying the use of the most advanced
services of Cloud platforms even in fields other than sports.
➤ Newesis is a pure technology based, Cloud Native company,
having as a target to support and evolve adoption of
DevOps culture and practices, with particular focus on
Kubernetes as technological platform.
➤ Twitter: @RaunoDepa
➤ Twitter: @newesissrl
3. AZURE WELL-ARCHITECTED FRAMEWORK –
SESSIONE 1 DI 6 - AGENDA
➤ Presentazione generale del percorso
➤ Cloud Computing – Concetti base
➤ Cloud Native Application – Principi fondamentali
➤ Microsoft Azure Well-Architected Framework - Introduzione
5. AZURE WELL-ARCHITECTED FRAMEWORK –
PERCORSO
➤ I Modulo: introduzione, principi e concetti base
➤ II Modulo: affidabilità
➤ III Modulo: sicurezza
➤ IV Modulo: ottimizzazione dei costi
➤ V Modulo: eccellenza operativa
➤ VI Modulo: efficienza delle prestazioni
6. AZURE WELL-ARCHITECTED FRAMEWORK –
OBIETTIVI
➤ Sapere valutare tra una opzione « Lift and shift» o «cloud optimised»
➤ Sapere valutare tra opzioni IaaS, PaaS e SaaS
➤ Sapersi orientare tra gli strumenti e le risorse di Microsoft Azure
➤ Sapersi orientare rispetto possibili scelte organizzative e definizioni di ruoli e responsabilità
in un ambito Cloud Native e DevOps
8. CLOUD COMPUTING – STORIA E CONCETTI
➤ «Il cloud computing (in italiano nuvola informatica) indica, in informatica, un paradigma di
erogazione di servizi offerti su richiesta da un fornitore a un cliente finale attraverso la rete
internet (come l'archiviazione, l'elaborazione o la trasmissione dati), a partire da un insieme
di risorse preesistenti, configurabili e disponibili in remoto sotto forma di architettura
distribuita.» (fonte: Wikipedia)
9. CLOUD COMPUTING – STORIA E CONCETTI
➤ 2002 Amazon crea Amazon Web Services (AWS)
➤ 2006 S3 and EC2 general availability (AWS)
➤ 2008 Google App Engine beta availability
➤ 2008 Microsoft crea la sua azienda di Cloud Computing (Azure)
➤ 2009 Alyum (Alibaba Cloud) viene fondata dal gruppi Alibaba in Cina
➤ 2010 Azure General availability
➤ 2010 Rakspace e NASA creano la piattaforma Open Source OpenStack
➤ 2011 IBM Cloud services general availability
➤ 2012 Google Cloud Compute Engine general availability
10. CLOUD COMPUTING – STORIA E CONCETTI
➤ Differente Tecnologia
➤ Nuovi modalità di utilizzo
12. CLOUD COMPUTING – STORIA E CONCETTI
➤ Dal Server al Serverless – da Infrastrutture a Servizi
13. CLOUD COMPUTING – STORIA E CONCETTI
Bisogna portare le applicazioni
nel Cloud e poi sottoporle a un
graduale processo di modifica
per farne collimare la struttura
con le nuove logiche distributive
e funzionali, come prevede il Lift
& shift?
Oppure, seguendo la logica del
Refactoring, è meglio riscriverle
ex novo, senza stravolgerne
interfaccia, funzionalità e
comportamento per adattarle da
subito alla modalità “as-a-
service”?
17. AZURE WELL-ARCHITECTED FRAMEWORK – CLOUD
NATIVE ARCHITECTURE
➤ Il principio dell'architettura per il cloud, noto anche come
architettura cloud-native, si concentra su come ottimizzare le
architetture di sistema per le capacità uniche del cloud.
➤ L'architettura tradizionale tende a ottimizzare per
un'infrastruttura fissa e ad alto costo, che richiede un notevole
sforzo manuale per la modifica.
➤ L'architettura tradizionale si concentra quindi sulla resilienza e
sulle prestazioni di un numero fisso relativamente piccolo di
componenti.
➤ Nel cloud, tuttavia, un'infrastruttura così fissa ha molto meno
senso perché il cloud viene addebitato in base all'utilizzo
(quindi risparmi denaro quando puoi ridurre l'ingombro) ed è
anche molto più facile da automatizzare (quindi l'aumento e la
riduzione automatici è molto più semplice ).
➤ Pertanto, l'architettura cloud-native si concentra sul
raggiungimento della resilienza e della scalabilità attraverso il
ridimensionamento orizzontale, l'elaborazione distribuita e
l'automazione della sostituzione dei componenti guasti.
18. AZURE WELL-ARCHITECTED FRAMEWORK – CLOUD
NATIVE ARCHITECTURE
➤ Disegnare per l’automazione:
➤ Infrastruttura (IaC): automatizzare la creazione
dell'infrastruttura, insieme agli aggiornamenti,
utilizzando gli strumenti Terraform
➤ Integrazione continua/Consegna continua (CI/CD):
automatizzare la creazione, il test e la distribuzione dei
pacchetti che compongono il sistema utilizzando
strumenti come Jenkins o Azure DevOps.
➤ Ridimensionamento: a meno che il carico del sistema
non cambi quasi mai, è necessario automatizzare
l'aumento e la riduzione del sistema in risposta
all'aumento del carico e la riduzione in risposta a cali di
carico prolungati
➤ Monitoraggio e ripristino automatizzato: eseguire il
monitoraggio e l'accesso ai sistemi cloud-native come
elemento fondante del ciclo di vita della soluzione.
19. AZURE WELL-ARCHITECTED FRAMEWORK – CLOUD
NATIVE ARCHITECTURE
➤ Gestione delle informazioni di stato
➤ Memorizzare lo "stato", che si tratti di dati utente (ad es. gli articoli nel
carrello degli acquisti degli utenti o del loro numero di dipendente) o di stato
del sistema (ad es. quante istanze di un lavoro sono in esecuzione, quale
versione del codice è in esecuzione in produzione) , è l'aspetto più difficile per
le soluzioni di un'architettura distribuita e nativa del cloud. Occorre quindi
progettare il sistema in modo che sia intenzionale su quando e come
archiviare lo stato e progettare i componenti in modo che siano senza stato
ovunque sia possibile.
➤ I componenti stateless sono facili da:
➤ Ridimensionare: per ridimensionare, aggiungi semplicemente più copie. Per
ridimensionare, chiudi le istanze di terminare una volta completata l'attività
corrente.
➤ Riparare: per "riparare" un'istanza guasta di un componente, è sufficiente
terminarla nel modo più elegante possibile e avviare una sostituzione.
➤ Rollback: se si dispone di una distribuzione errata, è molto più facile eseguire
il rollback dei componenti senza stato
➤ Bilanciare il carico: quando i componenti sono senza stato, il bilanciamento
del carico è molto più semplice poiché qualsiasi istanza può gestire qualsiasi
richiesta.
22. AZURE WELL-ARCHITECTED FRAMEWORK – CLOUD
NATIVE ARCHITECTURE
➤ Infrastructure as Code
➤ Configuration as Code
➤ Gestire le proprie infrastrutture come
«mandrie» e non come «cuccioli»
➤ «L'infrastruttura come codice (IaC) è il
processo di gestione e provisioning delle
risorse di computing nei data center
tramite file di definizione leggibili dalla
macchina, piuttosto che configurazione
hardware fisica o strumenti di
configurazione interattivi.» (fonte:
Wikipedia)
24. AZURE WELL-ARCHITECTED FRAMEWORK – CLOUD
NATIVE ARCHITECTURE
Donovan Brown – Principal DevOps Manager at
Microsoft
DevOps is the union of people, process, and products to
enable continuous delivery of value to our end users.
DevOps is not just automating a pipeline so we can
quickly deliver software. Our goal is to deliver value.
It is very important to realize that DevOps is not a
product.
You cannot buy DevOps and install it.
DevOps is not just automation or infrastructure as
code.
DevOps is people following a process enabled by
products to deliver value to our end users.
26. AZURE WELL-ARCHITECTED FRAMEWORK – CLOUD
NATIVE ARCHITECTURE
➤ “Observability is a measure of how well
internal states of a system can be inferred
from knowledge of its external outputs. In
control theory, the observability and
controllability of a linear system are
mathematical duals. The concept of
observability was introduced by
Hungarian-American engineer Rudolf E.
Kálmán for linear dynamic systems. A
dynamical system designed to estimate
the state of a system from measurements
of the outputs is called a state observer or
simply an observer for that system.”
27. AZURE WELL-ARCHITECTED FRAMEWORK – CLOUD
NATIVE ARCHITECTURE
➤ La raccolta di metriche e gli avvisi sono
attività guidate dal business.
➤ La raccolta di metriche e la gestione degli
avvisi sono cose diverse. È necessario
raccogliere metriche per avere visibilità sui
propri sistemi, ma non è necessario
utilizzare tutte le metriche per generare
avvisi.
➤ La misurazione, il monitoraggio e l'allerta
devono essere correlati agli SLO.
➤ Non avvisare per ogni evento, gli avvisi
devono segnalare un impatto sul servizio e
richiedere una azione.
29. AZURE WELL-ARCHITECTED FRAMEWORK –
INTRODUZIONE
➤ Azure Well-Architected Framework è una
serie di principi guida utilizzabili per
migliorare la qualità dei carichi di lavoro.
➤ Il framework è costituito da cinque elementi
fondamentali dell'eccellenza
dell'architettura:
➤ Affidabilità
➤ Sicurezza
➤ Ottimizzazione dei costi
➤ Eccellenza operativa
➤ Efficienza delle prestazioni
30. AZURE WELL-ARCHITECTED FRAMEWORK –
INTRODUZIONE
➤ Affidabilità
➤ Un carico di lavoro affidabile è sia resiliente che disponibile.
➤ La resilienza è la capacità del sistema di eseguire il ripristino in caso di errori e continuare a
funzionare.
➤ L'obiettivo della resilienza consiste nel ripristinare uno stato completamente funzionale
dell'applicazione dopo un errore.
➤ La disponibilità indica se gli utenti possono accedere al carico di lavoro quando è necessario.
31. AZURE WELL-ARCHITECTED FRAMEWORK –
INTRODUZIONE
➤ Affidabilità
➤ La creazione di un'applicazione affidabile nel cloud è diversa rispetto alla tradizionale
procedura di sviluppo delle applicazioni.
➤ Anche se in genere sono stati acquistati livelli di hardware ridondante di fascia alta per
ridurre al minimo le probabilità di errore di un'intera piattaforma applicativa, nel cloud è
stato riconosciuto in anticipo che si verificano errori.
➤ Invece di provare a evitare completamente gli errori, l'obiettivo deve essere quello di ridurre
al minimo gli effetti di un singolo componente in errore.
32. AZURE WELL-ARCHITECTED FRAMEWORK –
INTRODUZIONE
➤ Affidabilità
➤ La resilienza è la capacità di un sistema di correggere gli errori e continuare a funzionare.
➤ Ogni tecnologia ha modalità di errore specifiche che è necessario tenere in considerazione
durante la progettazione e l'implementazione di un'applicazione.
➤ Servizi di Azure specifici hanno caratteristiche diverse in termini di resilienza e di controlli e
correzioni automatiche.
34. AZURE WELL-ARCHITECTED FRAMEWORK –
INTRODUZIONE
➤ Sicurezza
➤ Si pensi alla sicurezza per l'intero ciclo di vita di un'applicazione, dalla progettazione e
implementazione alla distribuzione e alle operazioni.
➤ La piattaforma Azure offre protezione da varie minacce, ad esempio intrusioni di rete e
attacchi DDoS.
➤ È tuttavia necessario implementare la sicurezza nell'applicazione e nei processi DevOps
(DevSecOps).
35. AZURE WELL-ARCHITECTED FRAMEWORK –
INTRODUZIONE
➤ Sicurezza
➤ La sicurezza è uno degli aspetti essenziali di qualsiasi architettura. Offre garanzie di
riservatezza, integrità e disponibilità contro attacchi intenzionali e uso improprio di dati e
sistemi importanti.
➤ La perdita di queste garanzie può influire negativamente sulle operazioni e sui ricavi
aziendali e sulla reputazione dell'organizzazione.
➤ Per l'elemento fondamentale della sicurezza, verranno illustrati i principi e le considerazioni
chiave sull'architettura per la sicurezza e il modo in cui si applicano ad Azure.
39. AZURE WELL-ARCHITECTED FRAMEWORK –
INTRODUZIONE
➤ Ottimizzazione dei costi
➤ Quando si progetta una soluzione cloud, concentrarsi sulla generazione anticipata di valore
incrementale.
➤ Applicare i principi di creazione-misurazione-apprendimento per accelerare il time-to-market
evitando soluzioni a esborso intensivo di capitali.
40. AZURE WELL-ARCHITECTED FRAMEWORK –
INTRODUZIONE
➤ Ottimizzazione dei costi
➤ Il pilastro dell'ottimizzazione dei costi fornisce principi per il bilanciamento degli obiettivi
aziendali con una giustificazione del budget per creare un carico di lavoro conveniente
evitando soluzioni a elevato utilizzo di capitale.
➤ L'ottimizzazione dei costi riguarda l'analisi dei modi per ridurre le spese non necessarie e
migliorare l'efficienza operativa.
➤ Ogni scelta di progettazione ha implicazioni in termini di costi.
➤ Prima di scegliere un modello architetturale, un servizio di Azure o un modello di prezzo per
il servizio, prendere in considerazione i vincoli di budget impostati dall'azienda.
➤ Come parte della progettazione, identificare limiti accettabili su scala, ridondanza e
prestazioni rispetto ai costi.
41. AZURE WELL-ARCHITECTED FRAMEWORK –
INTRODUZIONE
➤ Ottimizzazione dei costi
➤ Considerare il monitoraggio e l'ottimizzazione dei costi come un
processo, anziché come un'attività temporizzazione.
➤ Eseguire revisioni dei costi regolari e misurare e prevedere le
esigenze di capacità in modo da poter effettuare il provisioning
delle risorse in modo dinamico e ridimensionare in base alla
domanda.
➤ Esaminare le raccomandazioni di gestione dei costi e intervenire
per ottimizzare i costi del carico di lavoro.
42. AZURE WELL-ARCHITECTED FRAMEWORK –
INTRODUZIONE
➤ Eccellenza Operativa
➤ L'eccellenza operativa riguarda le operazioni e i processi che mantengono un'applicazione in
esecuzione nell'ambiente di produzione. Le distribuzioni devono essere affidabili e
prevedibili.
➤ Automatizzare le distribuzioni per ridurre la probabilità di errori umani.
➤ I processi di distribuzione veloci e di routine non rallentano il rilascio di nuove funzionalità o
correzioni di bug.
➤ Altrettanto importante, è necessario eseguire rapidamente il rollback o il roll forward se un
aggiornamento presenta problemi.
43. AZURE WELL-ARCHITECTED FRAMEWORK –
INTRODUZIONE
➤ Eccellenza Operativa
➤ Il pilastro dell'eccellenza operativa riguarda i processi operativi che mantengono
un'applicazione in esecuzione nell'ambiente di produzione.
➤ Le distribuzioni devono essere affidabili e prevedibili.
➤ Le distribuzioni automatizzate riducono la probabilità di errori umani ed aumentano la
velocità con cui effettuare il rilascio di nuove funzionalità o correzioni di bug o l’esecuzione
di un rollback.
➤ Meccanismi di self-healing sono necessari per rendere l’automatismo realmente affidabile.
45. AZURE WELL-ARCHITECTED FRAMEWORK –
INTRODUZIONE
➤ Efficienza delle prestazioni
➤ L'efficienza delle prestazioni è la capacità del carico di lavoro di ridimensionarsi per
soddisfare le esigenze poste dagli utenti in modo efficiente.
➤ I modi principali per ottenere l'efficienza delle prestazioni includono l'uso appropriato della
scalabilità e l'implementazione di offerte PaaS con scalabilità incorporata.
46. AZURE WELL-ARCHITECTED FRAMEWORK –
INTRODUZIONE
➤ Efficienza delle prestazioni
➤ Comprendere le problematiche delle architetture distribuite
➤ La maggior parte delle distribuzioni cloud si basa su architetture distribuite in cui i
componenti vengono distribuiti tra vari servizi.
➤ La risoluzione dei problemi delle applicazioni monolitiche richiede spesso solo uno o due
obiettivi, ovvero l'applicazione e il database.
➤ Con le architetture distribuite, la risoluzione dei problemi è complessa e complessa a causa
di diversi fattori.
47. AZURE WELL-ARCHITECTED FRAMEWORK –
INTRODUZIONE
➤ Efficienza delle prestazioni
➤ Due modi principali per ridimensionare un'applicazione: il ridimensionamento verticale e il
ridimensionamento orizzontale.
➤ Il ridimensionamento verticale (aumento della scalabilità) aumenta la capacità di una risorsa,
ad esempio usando una macchina virtuale (VM) di dimensioni maggiori.
➤ Il ridimensionamento orizzontale (scalabilità orizzontale) aggiunge nuove istanze di una
risorsa, ad esempio macchine virtuali o repliche di database.
48. AZURE WELL-ARCHITECTED FRAMEWORK –
INTRODUZIONE
➤ Efficienza delle prestazioni
➤ La scalabilità orizzontale offre vantaggi significativi rispetto al ridimensionamento verticale, ad
esempio:
➤ Scalabilità cloud-native: le applicazioni sono progettate per l'esecuzione su centinaia o persino
migliaia di nodi, raggiungendo scale che non sono possibili in un singolo nodo.
➤ La scalabilità orizzontale è elastica: è possibile aggiungere altre istanze se il carico aumenta o
rimuovere istanze durante i periodi più brevi.
➤ La scalabilità orizzontale può essere attivata automaticamente, in base a una pianificazione o in
risposta alle variazioni del carico.
➤ La scalabilità orizzontale può essere più economica rispetto alla scalabilità verticale. L'esecuzione di
diverse macchine virtuali di piccole dimensioni può costare meno di una singola macchina virtuale
di grandi dimensioni.
➤ La scalabilità orizzontale può anche migliorare le resilienza aggiungendo la ridondanza. Se si arresta
un'istanza, l'applicazione continua a funzionare normalmente.
49. AZURE WELL-ARCHITECTED FRAMEWORK –
INTRODUZIONE
➤ Efficienza delle prestazioni
➤ La scalabilità orizzontale deve però essere progettata nel sistema.
➤ Oltre che dall’applicazione, nel cloud la possibilità di sfruttare la scalabilità dipende
dall'infrastruttura e dai servizi, con opzioni diverse nelle diverse soluzioni IaaS e PaaS.
50. AZURE WELL-ARCHITECTED FRAMEWORK –
INTRODUZIONE
➤ Efficienza delle prestazioni
➤ Stabilire linee di base delle prestazioni — Determina l'efficienza corrente dell'applicazione e della
relativa infrastruttura di supporto. La misurazione delle prestazioni rispetto alle baseline può offrire
strategie per miglioramenti e determinare se l'applicazione sta per raggiungere gli obiettivi
aziendali.
➤ Eseguire test di carico e stress — I test di carico misurano le prestazioni dell'applicazione in
quantità predeterminate di carico. I test di stress misurano il carico massimo che l'applicazione e la
relativa infrastruttura possono supportare prima che si allaccia.
➤ Identificare i colli di bottiglia — I colli di bottiglia sono un'area all'interno dell'applicazione che può
ostacolare le prestazioni. Questi punti possono essere il risultato di una mancanza di codice o di
una configurazione errata di un servizio. In genere, un collo di bottiglia peggiora con l'aumentare
del carico.
51. AZURE WELL-ARCHITECTED FRAMEWORK –
INTRODUZIONE
➤ Mettere insieme i cinque pilastri
➤ Affidabilità
➤ Sicurezza
➤ Ottimizzazione dei costi
➤ Eccellenza operativa
➤ Efficienza delle prestazioni
Azure Well-Architected Framework è una serie di principi guida utilizzabili per migliorare la qualità dei carichi di lavoro. Il framework è costituito da cinque elementi fondamentali dell'eccellenza dell'architettura:
Affidabilità - La capacità di un sistema di correggere gli errori e continuare a funzionare.
Sicurezza - Protezione delle applicazioni e dei dati dalle minacce.
Ottimizzazione dei costi - Gestione dei costi per massimizzare il valore offerto.
Eccellenza operativa - Processi operativi che mantengono un sistema in esecuzione in produzione.
Efficienza delle prestazioni - La capacità di un sistema di adattarsi ai cambiamenti di carico.
L'integrazione di questi elementi fondamentali consente di produrre un'architettura cloud di alta qualità, stabile ed efficiente:
Il Cloud offre diverse piattaforme, esistono quindi diversi modi di approcciare l’adozione del cloud per le varie soluzioni già in essere
Il Cloud offre diverse piattaforme, esistono quindi diversi modi di approcciare l’adozione del cloud per le varie soluzioni già in essere
Come orientarsi nella scelta su quale approccio verso il cloud seguire per ogni applicazione? Il valore di business diventa la chiave della valutazione, insieme alla complessità per la trasformazione
Un grado ancora maggiore di revisione è “Re-Architect” in cui si ripensa da zero la soluzione per realizzarla nuovamente secondo I principi cloud native.
Automatizzato – Ripetibile – Affidabile: queste sono le parole chiave di una soluzione CI/CD
Le linee guida:
Un manufatto per tutti gli ambienti: Non creare build diverse per ambienti diversi
Un processo per tutti gli ambienti: Non creare pipeline diverse per ambienti diversi
Ripara e non aggirare: Se un passaggio fallisce, deve essere corretto e mai aggirato
Niente al di fuori del repository: Il repository è l'unica fonte completa di verità
Più è complesso, più frequentemente deve essere affrontato: Le attività complesse diventano complicate se eseguite di rado
PET model
Management of each individual element of your infrastructure
Goals: each server part of your infrastructure should be available 24/7
CATTLE model
Manager of the overall infrastructure considering each element as disposable
Goals: solution\service uptime, considering that single elements will go down and will be destroyed and replaced
Movimento nato tra il 2008 e il 2009 (Patrick Dubois and Andrew Schafer) e poi cresciuto negli anni successivi. Nel 2011 inserito da Gartner nelle sue predizioni.
Negli stessi anni Google sviluppava la metodologia SRE separatametne ma coerentemente con i principi DevOps.
Principi SRE e DevOps
Distributed systems are difficult to monitor
Each system and application can provide a large amount of information about its status
Different information from the same system can be correlated
Traces reporting higher response time + Metrics reporting high CPU usage
Different information from different systems can be correlated
Traces from web application reporting high error rate + Logs from database system reporting high occurrence of deadlocks
Numerosi strumenti di sicurezza in Azure, ma anche pratiche per l’utilizzo di strumenti comuni
Responsabilità condivise in cloud
Un approccio DevSecOps
Scegliere le risorse giuste allineate con gli obiettivi aziendali e in grado di gestire le prestazioni del carico di lavoro. Un servizio non appropriato o non configurato correttamente può influire sui costi. Ad esempio, la creazione di un servizio in più aree quando i livelli di servizio non richiedono disponibilità elevata o la ridondanza geografica aumenterà i costi senza alcuna giustificazione aziendale ragionevole.