Serverless Code Camp
Gojko Adzic gojko@neuri.co.uk
Aleksandar Simovic alexander.simovic@gmail.com
A good hockey player plays
where the puck is. A great
hockey player plays where
the puck is going to be.
1
Wayne Gretzky
4 Amazon AWS Lambda
4 Google Cloud Services
4 Microsoft Azure Functions
4 IBM Open Whisk
Code with batteries included
4 Scaling
4 Monitoring
4 Recovery
4 Versioning
4 Logging
Traditional roles of servers taken over
by the platform
4 Gatekeeper -> Distributed Auth
4 Scaling point -> Containers
4 Orchestration -> Client or workflow engines
Strengths
4 Time to deploy minimal
4 Time to recover irrelevant
4 Multi-versioned
4 Forces small, isolated code modules
4 Fine-grained, transparent, cost of operation
4 Use readily-available services built for massive scale
Weaknesses
4 No strong SLAs yet
4 Latency
4 No PCI compliance
4 No way to keep open connections
4 Requires complete rethink on many common
practices
4 Configuration becomes a challenge
Opportunities
4 Skip a generation of technology/process upgrades
4 Rethink architectural and operational "best
practices"
4 Change billing models
4 Marketplaces for digital services
4 Fine-grained monitoring and optimisation
4 A/B testing throughout
Threats
4 Vendor lock-in (not code, but services)
4 High reliance on external parties
Key components
4 AWS Lambda - execute code
4 API Gateway - HTTP endpoint
4 DynamoDB - Storage (optional)
4 https://aws.amazon.com
Let's make some tanks
4 https://tankwars.serverless.camp/
4 https://github.com/awslabs/chalice
4 https://claudiajs.com/tutorials/

Serverless Code Camp Barcelona

  • 1.
    Serverless Code Camp GojkoAdzic gojko@neuri.co.uk Aleksandar Simovic alexander.simovic@gmail.com
  • 2.
    A good hockeyplayer plays where the puck is. A great hockey player plays where the puck is going to be. 1 Wayne Gretzky
  • 3.
    4 Amazon AWSLambda 4 Google Cloud Services 4 Microsoft Azure Functions 4 IBM Open Whisk
  • 4.
    Code with batteriesincluded 4 Scaling 4 Monitoring 4 Recovery 4 Versioning 4 Logging
  • 5.
    Traditional roles ofservers taken over by the platform
  • 6.
    4 Gatekeeper ->Distributed Auth 4 Scaling point -> Containers 4 Orchestration -> Client or workflow engines
  • 7.
    Strengths 4 Time todeploy minimal 4 Time to recover irrelevant 4 Multi-versioned 4 Forces small, isolated code modules 4 Fine-grained, transparent, cost of operation 4 Use readily-available services built for massive scale
  • 8.
    Weaknesses 4 No strongSLAs yet 4 Latency 4 No PCI compliance 4 No way to keep open connections 4 Requires complete rethink on many common practices 4 Configuration becomes a challenge
  • 9.
    Opportunities 4 Skip ageneration of technology/process upgrades 4 Rethink architectural and operational "best practices" 4 Change billing models 4 Marketplaces for digital services 4 Fine-grained monitoring and optimisation 4 A/B testing throughout
  • 10.
    Threats 4 Vendor lock-in(not code, but services) 4 High reliance on external parties
  • 11.
    Key components 4 AWSLambda - execute code 4 API Gateway - HTTP endpoint 4 DynamoDB - Storage (optional) 4 https://aws.amazon.com
  • 12.
    Let's make sometanks 4 https://tankwars.serverless.camp/ 4 https://github.com/awslabs/chalice 4 https://claudiajs.com/tutorials/