The document discusses microservices architecture and Azure services for building and hosting microservices. It describes how Azure supports microservices using PaaS options like App Service and Service Fabric. It also provides examples of implementing microservices using Cloud Services with Web and Worker roles along with features of App Service like deployments, backups and integrations.
2. Benefits of creating micro services in the cloud
End-To-End Use case for building cloud service with web &
worker roles with service bus integration
Azure App Service intelligent features including
troubleshooting, CI, back up, routing, scheduling & other
features
Azure Service Fabric microservices platform
3. A microservice is software building block that does one
thing and does it well.
Azure supports building loosely coupled systems using
micro services for web, mobile, IoT and Big Data solutions
that interact seamlessly in a persistent & highly available
platforms.
Microservices take advantage of automation, elasticity,
resilience of Azure IaaS & PaaS hosting options.
6. Is a PaaS hosted option in Microsoft Azure
A technology is designed to support apps that are scalable,
reliable, and cheap to operate
Hosted on Virtual Machines
You can remote access into Cloud Services VMs
Deploy highly-available, infinitely-scalable applications and
API
Focus on apps, not hardware.
Support for java, Node.js, PHP, Python, .NET and Ruby.
Auto scale to meet demand and save money (scale up or
down), Deploy thousands of instances in minutes
7. Any combination of these two slightly different VM hosting
options are available in a cloud service:
• Web role
Runs Windows Server with your web app automatically
deployed to IIS.
• Worker role
Runs Windows Server without IIS.
• You can add a console app as a web job in web role.
8. Flexible configuration per role in cloud services:
Configuration: # instances, size, startup endpoints
Settings: key/value
Endpoints
Storage
Certificates
Caching
10. An application that accepts user claims information and
process these requests “time consuming processing” into
other systems.
Implementation #1:
• User claims Web Role in a cloud service
• Process requests Worker Role in a cloud service
Implementation #2:
• User claims Web Role in a cloud service
• Process requests A Web Job in a web role
11.
12. Azure App Service is a cloud app service that integrates
everything you need to quickly and easily build web and
mobile apps for any platform or device.
Code in your favorite language and IDE.
Use .NET, NodeJS, PHP, Python, Java to build web apps or
APIs faster than ever.
Scale apps on-demand with high availability.
Broadcast personalized push notifications to millions in
minutes
13.
14. App Service offers:
Support and troubleshooting features
Resource health
App Service Advisor
New support Ticket
Easy to scale up or out for service plans
MySQL in App (preview)
15. App Service offers
Kudu services: process explorer,
debug console, Files, PS..etc.
Performance test: create load tests
Extensions
Testing in production
Console
Clone app
16. Easy to publish code from various repositories:
VSTS, OneDrive, Local Git repo, GitHub,
BitBucket, Dropbox & External repository.
Deployment creds to share for FTP clients
Easy to manage multiple deployment slots
A great way manage continuous builds
Integrate with VSTS build server to automate builds
17. The ability to add webjobs within the same deployments
Manage custom domains and SSL certificates
Setup Networking configuration
Define APIs settings Urls
Configure CORS settings
Traffic routing per deployment slot
Automated and scheduled backups
Custom domains & SSL configuration
18.
19. Service Fabric is a distributed systems platform that
makes it easy to package, deploy, and manage
scalable and reliable microservices and addresses
the significant challenges in developing and
managing cloud applications.
Service Fabric represents the next-generation
middleware platform for building & managing these
enterprise-class, Tier-1 cloud-scale applications.
24. Benefits of creating micro services in the cloud
End-To-End Use case for building cloud service with web &
worker roles with service bus integration
Azure App Service intelligent features including
troubleshooting, CI, back up, routing, scheduling & other
features
Azure Service Fabric microservices platform
Notes de l'éditeur
The session covers how to build web, mobile, Api solutions using Microsoft Azure platform. The session covers in detail how to build intelligent solutions using Azure App Service. Azure App Service includes web apps, logic apps and mobile apps services as PaaS solutions for engineers. The session is a demo driven and demonstrate how to design and provision complete end-to-end solutions using Microsoft intelligent cloud.
Elastic: capable of returning to the original form.
Resilience: capable of running strong and healthy after something bad happens.
This demo uses Web and worker roles, service bus and Azure tables. The demos shows how to use Cloud Explorer to check Azure component.
Sample Url:
http://weblogs.asp.net/shijuvarghese/building-windows-azure-cloud-services-app-with-web-role-worker-role-table-storage-and-service-bus
Sample Git:
https://github.com/shijuvar/AzureCloudServices/blob/master/AzureCloudServices/AzureCloudServices.Web/Views/Customer/Create.cshtml
Accessing Kudu Service: https://sflccmobileapp1.scm.azurewebsites.net/
Accessing Kudu Service: https://sflccmobileapp1.scm.azurewebsites.net/
Testing in production feature:
https://azure.microsoft.com/en-us/documentation/articles/app-service-web-test-in-production-get-start/
Accessing Kudu Service: https://sflccmobileapp1.scm.azurewebsites.net/
Accessing Kudu Service: https://sflccmobileapp1.scm.azurewebsites.net/
Showing:
Troubleshooting features:
Kudu
Logs
Troubleshooting
Support ticket
Scale up or out options
Kudu service
API and CORS
Backup options ( scheduled option )
Custom Domains & SSL
Optional:
Ref.: https://azure.microsoft.com/en-us/documentation/articles/service-fabric-overview/
Service Fabric is tailored to creating “born in the cloud” services that can start small, as needed, and grow to massive scale with hundreds or thousands of machines.
Ref.: https://azure.microsoft.com/en-us/documentation/articles/service-fabric-overview/
You can create Service Fabric clusters in many environments to deploy your applications to. This can be in Azure or on premises, on Windows Server or on Linux.
In addition the development environment in the SDK is identical to the production environment with no emulators involved. In other words, if it runs on your local development cluster it will deploy to the same cluster in other environments.
Reliable Services can be stateless, similar to most service platforms, such as web servers or Worker Roles in Azure Cloud Services, in which each instance of the service is created equal and state is persisted in an external solution, such as Azure DB or Azure Table Storage.
Reliable Services can also be stateful, exclusive to Service Fabric, where state is persisted directly in the service itself using Reliable Collections. State is made highly-available through replication and distributed through partitioning, all managed automatically by Service Fabric.
Ref.: https://azure.microsoft.com/en-us/documentation/articles/service-fabric-choose-framework/
Reliable Services: https://azure.microsoft.com/en-us/documentation/articles/service-fabric-reliable-services-introduction/
Reliable Actors: https://azure.microsoft.com/en-us/documentation/articles/service-fabric-reliable-actors-introduction/