No Server, No Cry; Introducing Serverless

Transcript

1. No Server, No Cry Introducing Serverless @daronyondem http://daron.me

2. How does the cloud look today?

3. None
4. None

5. What’s bad with containers? • Containers are the new VMs!

   • Server Patching > Container Image Batching • Container Orchestration is hard.

6. “Everything's gonna be all right!” Bob Marley

7. What is serverless? It’s the way cloud should be!

8. Serverless architectures refer to applications that significantly depend on third-party

   services (knows as Backend as a Service or "BaaS") or on custom code that's run in ephemeral containers (Function as a Service or "FaaS") Martin Fowler

9. What I understand? • Worry/care just about your code. •

   Pay per use metering units at max optimization. (GB/s) • No commitment, no hardware provisioning (really?)

10. Serverless != Microservices • You can have a fleet of

    EC2 instances, running containers, orchestrating and still worry about infrastructure. • You can have dozens of functions tightly coupled and delivered as a behemoth.

11. Azure Functions 101 • C# Script, .NET Libraries, F#, JavaScript,

    Java • Schedule, Http, Storage, Queues, SQL, CosmosDB, Push Notifications, Twilio, SendGrid, Microsoft Graph, Webhooks.

12. DEMO

13. Function Proxies

14. Durable Functions

15. None

16. Resources / Links • Documentation • https://docs.microsoft.com/en-us/azure/azure-functions/ • Azure Functions

    Runtime (Run on-prem) • https://docs.microsoft.com/en-us/azure/azure- functions/functions-runtime-overview

17. Thanks! Slides here => http://daron.me/decks Daron Yöndem http://daron.me | @daronyondem