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

The SaaS Journey on AWS

The SaaS Journey on AWS

From an event run in conjunction with AWS, this slide deck covers some of the architectural considerations you'll want to consider as you build your SaaS solution out on the AWS cloud.

The Scale Factory

November 26, 2019

More Decks by The Scale Factory

Other Decks in Technology


  1. Empowering you to deliver more with the AWS Cloud Consultancy

    Engineering Support Training @scalefactory
  2. THE SCALE FACTORY WAY_ People First Match solution to workload

    Leverage the AWS platform Automate Iterate
  3. YOUR PRODUCT_ B2B or B2C? How many customers? Where are

    they? How much do they pay? Are there any regulatory considerations?
  4. ARCHITECTURE CUSTOMER NEEDS (things you care about) COMPLIANCE NEEDS (things

    the government cares about) Features Cost Performance Availability Security Security Documentation Reporting Change Control
  5. TENANCY OPTIONS All Tenants Tenant 1 Tenant 2 All Tenants

    Tenant 1 Tenant 2 POOL BRIDGE SILO Cost Isolation Complexity Lowest Highest
  6. TENANT ISOLATION_ AWS Account Layer VPC Layer Subnet Layer Container

    Layer Application Layer Operational Complexity Lowest Highest Isolation Usage Transparency Cost
  7. Visible Invisible Value Chain Evolution Genesis Custom Product Commodity Power

    Customer MySQL Compute Storage Data Centre HA Scripts Monitoring Config Mgmt Networking
  8. A CASE FOR SERVERLESS_ Scales with demand No cost for

    idle resources No traditional server maintenance Spend developer time on business value
  9. AMAZON API GATEWAY_ OpenAPI definition Authentication / Authorization Quotas and

    throttling Result caching Lifecycle management Direct integration with AWS services
  10. AMAZON COGNITO_ User directory Social & Enterprise identity federation MFA

    Role based access control Compromised credential protection
  11. { "Version": "2012-10-17", "Statement": [ { "Effect": "Allow", "Action": [

    "dynamodb:GetItem", "dynamodb:BatchGetItem", "dynamodb:Query", "dynamodb:PutItem", "dynamodb:UpdateItem", "dynamodb:DeleteItem", "dynamodb:BatchWriteItem" ], "Resource": [ "arn:aws:dynamodb:us-west-2:123456789012:table/MyTable" ], "Condition": { "ForAllValues:StringEquals": { "dynamodb:LeadingKeys": ["${cognito-identity.amazonaws.com:sub}"] } } } ] }
  12. Deployment Frequency Lead Time for Changes Time to Restore Service

    Change Failure Rate WHAT TO MONITOR: DEVOPS_
  13. Aspect of So ware Delivery Performance* Elite High Medium Low

    Deployment frequency For the primary application or service you work on, how o en does your organization deploy code to production or release it to end users? On-demand (multiple deploys per day) Between once per day and once per week Between once per week and once per month Between once per month and once every six months Lead time for changes For the primary application or service you work on, what is your lead time for changes (i.e., how long does it take to go from code committed to code successfully running in production)? Less than one day Between one day and one week Between one week and one month Between one month and six months Time to restore service For the primary application or service you work on, how long does it generally take to restore service when a service incident or a defect that impacts users occurs (e.g., unplanned outage or service impairment)? Less than one hour Less than one daya Less than one daya Between one week and one month Change failure rate For the primary application or service you work on, what percentage of changes to production or released to users result in degraded service (e.g., lead to service impairment or service outage) and subsequently require remediation (e.g., require a hotfix, rollback, fix forward, patch)? 0-15%b,c 0-15%b,d 0-15%c,d 46-60% https:/ /cloud.google.com/blog/products/devops-sre/the-2019-accelerate-state-of-devops-elite-performance-productivity-and-scaling
  14. CLOSING RECAP_ Design for a pooled tenancy model first Leverage

    the AWS services Use the AWS security features Monitoring as first class citizen