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.

Transcript

1. THE SAAS JOURNEY ON AWS_
2. Empowering you to deliver more with the AWS Cloud Consultancy Engineering Support Training @scalefactory
3. THE TEAM_
4. OUR CLIENTS_
6. TODAY’S AGENDA_ Tenancy Options Relevant AWS Services Security Considerations Monitoring
7. THE SCALE FACTORY WAY_ People First Match solution to workload Leverage the AWS platform Automate Iterate
8. YOUR PRODUCT_ B2B or B2C? How many customers? Where are they? How much do they pay? Are there any regulatory considerations?
9. ARCHITECTURE CUSTOMER NEEDS (things you care about) COMPLIANCE NEEDS (things the government cares about) Features Cost Performance Availability Security Security Documentation Reporting Change Control
10. TENANCY OPTIONS All Tenants Tenant 1 Tenant 2 All Tenants Tenant 1 Tenant 2 POOL BRIDGE SILO Cost Isolation Complexity Lowest Highest
11. TENANT ISOLATION_ AWS Account Layer VPC Layer Subnet Layer Container Layer Application Layer Operational Complexity Lowest Highest Isolation Usage Transparency Cost
12. CASE STUDY_
13. BRIDGE TENANCY MODEL_
15. LEVERAGE AWS SERVICES_
17. Visible Invisible Value Chain Evolution Genesis Custom Product Commodity Power Customer MySQL Compute Storage Data Centre HA Scripts Monitoring Config Mgmt Networking
18. Visible Invisible Value Chain Evolution Genesis Custom Product Commodity Customer RDS Aurora
20. RELEVANT SERVICES_ Amazon API Gateway Amazon Cognito SNS / SQS DynamoDB S3 Lambda
21. RELEVANT SERVICES_ Amazon API Gateway Amazon Cognito SNS / SQS DynamoDB S3 Lambda }Serverless
22. A CASE FOR SERVERLESS_ Scales with demand No cost for idle resources No traditional server maintenance Spend developer time on business value
23. AMAZON API GATEWAY_ OpenAPI definition Authentication / Authorization Quotas and throttling Result caching Lifecycle management Direct integration with AWS services
24. AMAZON COGNITO_ User directory Social & Enterprise identity federation MFA Role based access control Compromised credential protection
25. APPLICATION LAYER ISOLATION_
27. { "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}"] } } } ] }
28. FINE GRAINED POLICIES_ KMS key policies S3 bucket policies SNS Secrets Manager
29. Somebody Else's Problem
30. CASE STUDY_
32. APPLICATION MONITORING_
33. WHAT TO MONITOR: USAGE_ Cost IO usage Storage usage CPU usage
34. Request rate Errors Performance WHAT TO MONITOR: SERVICE_
35. User activity Helpdesk load WHAT TO MONITOR: HUMAN_
36. Deployment Frequency Lead Time for Changes Time to Restore Service Change Failure Rate WHAT TO MONITOR: DEVOPS_
37. 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
38. CLOSING RECAP_ Design for a pooled tenancy model first Leverage the AWS services Use the AWS security features Monitoring as first class citizen
39. WHAT'S NEXT?_ @scalefactory
40. TODAY: ASK AN ARCHITECT_
41. TALK TO US ABOUT: CONSULTANCY TRAINING WELL-ARCHITECTED MIGRATION