Upgrade to Pro — share decks privately, control downloads, hide ads and more …

No Server, No Cry; Introducing Serverless

Daron Yondem
November 15, 2017

No Server, No Cry; Introducing Serverless

This a presentation I hosted during the Webrazzi Developer 2017 conference in Istanbul.

Daron Yondem

November 15, 2017
Tweet

More Decks by Daron Yondem

Other Decks in Programming

Transcript

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

    • Server Patching > Container Image Batching • Container Orchestration is hard.
  2. 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
  3. 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?)
  4. 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.
  5. Azure Functions 101 • C# Script, .NET Libraries, F#, JavaScript,

    Java • Schedule, Http, Storage, Queues, SQL, CosmosDB, Push Notifications, Twilio, SendGrid, Microsoft Graph, Webhooks.
  6. 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