Going serverless
•Télécharger en tant que PPTX, PDF•
1 j'aime•1,795 vues
Steve Lee talks about going serverless using Microsoft Azure at TechExeter on 25th August 2016 www.techexeter.uk
Recommandé
Recommandé
Contenu connexe
Tendances
Tendances (20)
En vedette
En vedette (20)
Similaire à Going serverless
Similaire à Going serverless (20)
Plus de TechExeter
Plus de TechExeter (20)
Dernier
Dernier (20)
Going serverless
- 1. Serverless with Azure Apps STEVE LEE, OPENDIRECTIVE, TECHEXETER 25 AUG 2016 © 2016 STEVE LEE ATTRIBUTION-SHAREALIKE 4.0 INTERNATIONAL
- 3. The Cloud
- 4. Value Proposition: Easier DevOps through outsourcing
- 5. Microsoft Azure “A growing collection of integrated cloud services” Microsoft “…winning developers with a kinder, gentler cloud” TechRepublic
- 6. Do it yourself server Self managed stack App|API + Data Server Runtime Hardware + Network OS Your Wizzy App PHP + MySQL + Apache Linux Dusty old box
- 7. Platform as a Service - PaaS Concentrate on your stuff App | API + Data Server Runtime Hardware + Network OS Configure Dev + Test + Deploy
- 8. Serverless New kid on the block App | API + Data Server Runtime Hardware + Network OS Logic fragments Nanoservices!
- 9. Mobile App or Single Page Web App (javascript) App (client) PaaS ServicesServices + SaaS Push Eg HTTP + JSON + JWT API server Client Services S D K
- 10. Azure Mobile Apps Backend as a Service – BaaS App Auth Sync Push S D K API + Swagger Services3rd Party SaaS S D K
- 12. Azure Functions Functions as a Service Functions that run in ephemeral containers Choice of languages Connectors: Timer, Services, HTTP web hooks PAYG Open Source
- 14. Azure LogicApps Workflow as a Service Integration and automating business processes Declarative event driven workflows – JSON + DSL Graphic designer Connectors: Time, Services, HTTP webhooks Automation API PAYG or plan
- 15. Demo
Notes de l'éditeur
- From PC under your desk to Room full of kit and air con
- Outsource part of the stack to a cloud provider
- An ancient, pervasive and flexible system architectural pattern. Look hard and you find it everywhere, in many variations. Thin or Thick client, even UI as server (X11)
- Server responds with HTML Static / dynamic
- Flexible client / server split and supporting protocols RESTful +with JSON payload very common Use many other services
- Flexible client / server split and supporting protocols RESTful +with JSON payload very common Use many other services
- Flexible client / server split and supporting protocols RESTful +with JSON payload very common Use many other services
- Flexible client / server split and supporting protocols RESTful +with JSON payload very common Use many other services