20170209 dev day-websites_vs_cloudservices_vsservicefabric_scenarios
•
0 likes•40 views
This document discusses different Azure cloud services including Cloud Services, Service Fabric, and App Services. It provides an overview of each service, comparing their key features such as scalability, deployment options, programming models, and support for different languages. Cloud Services provide virtual machines and web/worker roles. Service Fabric is a distributed systems platform for microservices. App Services consolidate web sites, mobile apps, APIs, and logic apps into a single integrated offering.
Recommended
Recommended
More Related Content
What's hot
What's hot (20)
Similar to 20170209 dev day-websites_vs_cloudservices_vsservicefabric_scenarios
Similar to 20170209 dev day-websites_vs_cloudservices_vsservicefabric_scenarios (20)
More from Ricardo González
More from Ricardo González (20)
Recently uploaded
Recently uploaded (20)
20170209 dev day-websites_vs_cloudservices_vsservicefabric_scenarios
- 1. Azure Cloud: Cloud Services, Service Fabric y App Services, Escenarios de Aplicación Ricardo Gonzalez Vargas Microsoft Regional Director - Bogotá CEO – Androcial Media Inc. / WomyAds.com @rgonv http://ricardogonzalez.me
- 3. Por que la nube? Managedbyvendor Infrastructure (as a Service) Youscale,make resilient&manage Platform (as a Service) Scale,resilienceand managementbyvendor Youmanage On Premises Youscale,makeresilientandmanage Applications Software (as a Service) Scale,resilienceand managementbyvendor
- 4. Maquinas Virtuales • Alto control • Alta flexibilidad • Integración On-Premise • Administrado por el cliente • OS • Actualizaciones • Parches
- 5. Azure App Service: Una oferta integrada API Apps Easily build and consume APIs in the cloud Web Apps Web apps that scale with your business Mobile Apps Build Mobile apps for any device Logic Apps Automate business process across SaaS and on-premises
- 6. Azure App Service • Consolida y reemplaza Servicios existentes: • Azure Web Sites, Azure BizTalk Services, Azure Web API Authoring, Azure Mobile Services • Crear experiencias web y móviles que comparten acceso a datos y lógica de negocio • Automatización de procesos de negocio con logic apps • Construcción de APIs o consumo de conectores del Marketplace • Un modelo unificado de facturación para todos los Servicios • Un Gateway común para autenticación
- 7. Multi-tenant. Daily quotas Multi-tenant. No quotas Dedicated VMs. No quotas
- 8. reserved
- 9. reserved
- 10. SHARED INSTANCES
- 14. Que es un Cloud Service?
- 17. Dominios de Falla • Requiere 2 o mas instancias por role • Los dominios aíslan las VMs • Los dominios proveen redundancia • Al menos dos dominios por role
- 18. Un arquetipo de aplicacion con alta escalabilidad
- 24. Azure Service Fabric • Azure Service Fabric es una plataforma distribuida que facilita el empaquetamiento, despliegue y administracion de aplicaciones escalables y confiables. • Facilita el desarrollo orientado a microservicios • Abstrae la complejidad de los problemas de infraestructura, facilitando el despliegue, replicacion y Versionamiento de las aplicaciones
- 25. Arquitectura de Servicios en la nube traditional User Interface Business Logic Data User Interface Business Logic Data Microservices Features Scalability Manage Services Deliver Features Faster Create Business Value Availability Latency Lifecycle Data Integrity Portability
- 26. Microsoft Azure Service Fabric Una platforma para apps basadas en microservicios confiables e hiperescalables Microservices Azure Windows Server Linux Hosted Clouds Windows Server Linux Service Fabric Private Clouds Windows Server Linux High Availability Hyper-Scale Hybrid Operations High Density Rolling Upgrades Stateful services Low Latency Fast startup & shutdown Container Orchestration & lifecycle management Replication & Failover Simple programming models Load balancing Self-healingData Partitioning Automated Rollback Health Monitoring Placement Constraints
- 27. Un conjunto de maquinas independientes, fisicas o virtuales Centro de datos comun
- 28. Cluster: una federacion de maquinas Node Node Node Node Node Node
- 29. Application: Grupo lógico de microservicios Application Container Container Container Container
- 30. Deteccion de fallas de una maquina Time = t1 83 76 50 46 64 New Node arrived61 Time = t2 83 61 50 46 Failures Detected cluster reconfigured 83 76 64 50 46 Time = t0 Nodes failed
- 31. Ubicación y recuperación de Microservices Node 103 P S S Node 104 S S Node 102 P S S S Node 105 P S S S Node 101 S S P Node 100 S P S S P S S S
- 32. Cluster: Vista de sistema System Services Failover manager Cluster manager Naming Image store
- 33. Queues Storage Patron de servicios en tres capas Front End (Stateless Web) Stateless Middle-tier Compute Cache • Escala con almacenamiento particionado • Aumenta la confiabilidad con colas • Reduce latencia con cache • Administra sus transacciones para consistencia del estado • Muchas piezas administradas de forma separada Load Balancer
- 34. Stateful Middle-tier Compute Servicios con estado: Diseño simplificado y reducción de latencia Front End (Stateless Web) data stores used for analytics and disaster recovery • El estado de la aplicacion vive en la capa de computo • Baja latencia para lecturas y escrituras • Las particiones son punto base para escalar • Soporte a transacciones • Menos componentes Load Balancer
- 35. Comparación de características Feature App Service (web apps) Cloud Services (web roles) Virtual Machines Service Fabric Near-instant deployment X X Scale up to larger machines without redeploy X X Web server instances share content and configuration, which means you don't have to redeploy or reconfigure as you scale. X X Multiple deployment environments (production and staging) X X X Automatic OS update management X X Seamless platform switching (easily move between 32 bit and 64 bit) X X Deploy code with GIT, FTP X X Deploy code with Web Deploy X X WebMatrix support X X Access to services like Service Bus, Storage, SQL Database X X X X Host web or web services tier of a multi-tier architecture X X X X Host middle tier of a multi-tier architecture X X X X
- 36. Comparación de características Feature App Service (web apps) Cloud Services (web roles) Virtual Machines Service Fabric Integrated MySQL-as-a-service support X X X Support for ASP.NET, classic ASP, Node.js, PHP, Python X X X X Scale out to multiple instances without redeploy X X X X Support for SSL X X X X Visual Studio integration X X X X Remote Debugging X X X Deploy code with TFS X X X X Network isolation with Azure Virtual Network X X X X Support for Azure Traffic Manager X X X X Integrated Endpoint Monitoring X X X Remote desktop access to servers X X X Install any custom MSI X X X Ability to define/execute start-up tasks X X X Can listen to ETW events X X X
- 39. Gracias! Ricardo Gonzalez Vargas Microsoft Regional Director - Bogotá CEO – Androcial Media Inc. / WomyAds.com @rgonv http://ricardogonzalez.me
Editor's Notes
- Slide Objectives: Explain the three scale choices on Windows Azure Web Sites. Notes: Both free and shared are the same architecture. The only difference is that free has quotas where as with shared you can use and pay for as much resources as you choose. With reserved you isolate your application to your own virtual machines that you can use and pay for whatever resources you choose.
- Slide Objectives: Explain how you can start with a small site hosted for free. Notes:
- Slide Objectives: Explain how you can scale your site to multiple shared instances. Notes:
- Slide Objectives: Explain how you can move to reserved instances for additional scale. Notes:
- Slide Objectives: Explain how you can scale up reserved instances to multiple instances as needed. Notes:
- Slide Objectives: Explain how you can host multiple sites that you own on a your reserved instances. Notes:
- Note: VM is separated out as IaaS offering.
- Slide Objective Understand the difference between Roles and Instances Speaker Notes The Service model defines the shape of a service- the Roles it will have endpoints it will listen on Types of VMs that will be run At runtime each Role will run at a given scale Specifically each role will be deployed onto and executed on one or more VMs A VM runs a single role Notes Notes on the various security roles involved in running a Windows Azure account http://blog.toddysm.com/2010/01/subscription-and-service-administration-in-windows-azure.html
- The infrastructure of each Windows Azure data center is notionally divided into multiple sections known as fault domains. These sections of the infrastructure (which are not necessarily individual servers or server racks) are designed in such a way that a failure of one fault domain is extremely unlikely to affect any other fault domain. When you deploy a service, the Windows Azure Fabric Controller automatically locates the roles in at least two different fault domains so that a failure in one domain will not affect all instances of your service.
- Slide Objective Understand what a scale-out application looks like Speaking notes High scale applications often follow this sort of an pattern Inbound connectivity comes through a load balancer Requests are round robin routed Load balancer is typically aware of the state of the web servers (i.e. are they up) There are one or more tiers or groups of stateless web or app servers By stateless we mean that they do not hold state between client requests Stateless means that simple load balancing works – no need for sticky sessions Stateless means that the failure of a web server does not cause major issues for application- it is simply removed from the load balancer A stateful or storage tier This will generally involve some sort of scale out approach for large apps Often using partitioned databases Often some sort of queuing mechanism Applications will often perform processing in the background. Improves response time for users Allows load peaks to be buffered in queues Windows Azure provides us with a Platform as a Service offering to implement these sorts of applications Notes http://msdn.microsoft.com/en-us/magazine/cc500561.aspx http://msdn.microsoft.com/en-us/library/ff650667.aspx
- Slide Objective Understand the 3 common patterns of worker roles Speaker Notes Pattern 1 – Polling Worker role polls a Queue Pops message Performs work Polls queue again Pattern 2 Worker listens for inbound TCP request Can implement with Raw TcpListeners or use WCF or use Hosted Web Core Pattern 3 Run a 3rd party process When the role starts up or runs use a Process.Start() call to run a standard windows executable E.g. Running a database server Notes http://blog.smarx.com/posts/build-your-own-web-role-running-hosted-web-core-in-windows-azure http://blog.smarx.com/posts/making-songs-swing-with-windows-azure-python-and-the-echo-nest-api
- Slide Objective Understand how a Web Role extends the standard worker role Speaker Notes A web role takes all the capabilities and semantics of a worker role and adds the IIS Hostable Web Core Web Roles run ASP.NET websites- they do this by using the IIS hostage web core. pretty much anything that will work in a standard IIS ASP.NET Web Site should work in Windows Azure. At MIX09, we additionally added support for IIS7’s FastCGI capability. As a note, any files that are part of a asp.net project on windows azure are READ ONLY! If you need to be able to change the contents of files: User Blob Storage If its configuration, use the service model files – which can be changed at runtime. Inbound protocols are http(s) – outbound protocols are any TCP connection but NOT UDP. Notes http://msdn.microsoft.com/en-us/library/dd179341.aspx http://blogs.msdn.com/b/carlosag/archive/2008/04/14/hostyourownwebserverusingiis7.aspx http://blogs.iis.net/ksingla/archive/2007/12/20/ins-amp-outs-of-hostable-web-core.aspx
- Slide Objective To understand how and why to change the VM Size for a Windows Azure role Slide Notes When you create your service model, you can specify the size of the virtual machine (VM) to which to deploy instances of your role, depending on its resource requirements. The size of the VM determines the number of CPU cores the memory capacity the local file system size allocated to a running instance Each physical machine in Windows Azure contains 8 processor cores. You need to specify an XL instance to reserve an entire machine Network is shared but burstable Can burst beyond your 1/8th allocation when using a small VM May be limited to just your allocation For guaranteed high network throughput use an XL VM Not http://msdn.microsoft.com/en-us/library/ee814754.aspxes