Agenda
    Justification
    Application requirements
    AWS serverless architecture
    Frameworks and tooling
    Gotchas
    Questions
   What’s the business case?
    Know why you are building in the cloud 
    before you start
      Hint: It’s probably not to save money
    Some ideas
      Improve responsiveness to customer needs
      Centralize and automate resource management
      Document and version environment
      Support cyclic or shifting usage patterns (match 
      supply with demand)
      Develop skillsets
   AWS Application Models
    Lift-and-shift
     Take existing virtual machines and move them to 
     cloud-hosted EC2 instances (rehost)
     Quickest and cheapest, but fewest cloud 
     advantages
    Rearchitect
     Rebuild application from the ground up using 
     managed services
     Most time consuming and expensive, but most 
     cloud advantages
   Requirements
    Basic CRUD operations
     Create, read, update, delete
    Multi-user
    Scalable
    Secure (authentication and authorization)
    Use managed resources
     Align with AWS best practices
  Annual Equipment Request App
   Used to manage the Library’s annual 
   purchase and prioritization cycle
   20 users with varied roles and permissions
   Create, list, update, delete records
   Old, ready for rework
   Big enough to be non trivial, small enough 
   that we had a chance of success
   Built with PHP (Laravel), jQuery, SQL Server