Please enable JavaScript.

Coggle requires JavaScript to display documents.

Serverless DotNetNorth (Part 2 (VPC Attachment (Use Case (Normally…

- - - - Part 1
      - Part 2
    - - AWS
        
        Other cloud providers exist
        
        Google Cloud Functions
        
        Azure Functions
      - Serverless Framework
  - - - Functions
        
        Lambda
      - Managed Services
        
        API Gateway
        
        Secrets Manager
        
        DynamoDB
      - Serverless makes things easier to get up and running
      - Get to MVP sooner
      - Benefits
        
        Scales with demand automatically
        
        Significantly reduces costs (against servers) - don't pay for idle
        
        Eliminates server maintenance
        
        Frees resource to work on building things -rather than maintaining
    - - No Servers
      - No operations
      - A silver bullet
    - - Fender
      - Netflix
      - AO.com
    - - Observaibility
      - Latency
      - Reliance on vendors
  - - - Brief description of serverless yml
      - Amend serverless yml
      - Deploy serverless yml
      - serverless invoke
      - Show in dashboard
      - serverless create
    - - Options (Languages)
    - - We've got a function
      - It's pretty useless as things stand
      - Triggers
      - Create a http endpoint trigger
        
        APIGateway Request
        
        Headers
        
        APIGateway Response
        
        Why is this needed?
        
        API Keys
      - Create a cron job trigger
        
        CloudWatch Event
      - Storing data
        
        Options
        
        DynamoDB
        
        IAM Roles
- - - - Introduced Serverless as a concept
      - Created a service
      - Triggered via http and cron job
  - - - Normally connectivity to a database
        
        Using external data sources
        
        VPC Peering
        
        MongoDB Atlas
      - Any connectvitiy internal to a VPC
      - Any connectivity you want to keep private
    - - What is a cold start
        
        The time to initialise a function on first invocation
        
        Language choice has an impact
        
        Memory allocation has an impact
      - ENI interface
      - What can you do about it?
        
        Cloudwatch Hack
        
        Predict busy periods and pre-warm
    - - Impact with memory allocation
    - - Direct Link
      - VPC Endpoints
  - - - This is the limit that forced us to stop and think
    - - Share domain names
      - Share API keys
      - Create multiple services
    - - One big service file (takes time)
      - Do we want to deploy everything all the time?
      - How did we approach this?
      - How can we not deploy everything, all the time?
      - How can we share dependencies (queues, databases etc...)
    - - When we deploy one thing - everything else needs deploying with it
      - Traditionaly, think of tightly coupled systems
      - In Serverless - everything in one serverless.yml
  - - - Define
      - Every commit leads to release
      - Pairs with Serverless really well
        
        Why
        
        Small units of code
        
        Microservices to the extreme
        
        Independently deployable by design
  - - - Part 1
      - Part 2
    - - YES
      - Time to market
      - Less operational burden
      - Lots to learn
        
        Have an open mindset
        
        Accept responsibility of system