Building on AWS Cloud One Codebase Aberdeen 25-apr-19
•Download as PPTX, PDF•
0 likes•426 views
How do you build a business and applications on AWS? What are the mindsets and frameworks that successful orgs use? What choices do they make, and what do they avoid? What can we learn from other orgs successes with case studies, and how do you get started?
Recommended
Recommended
More Related Content
Similar to Building on AWS Cloud One Codebase Aberdeen 25-apr-19
Similar to Building on AWS Cloud One Codebase Aberdeen 25-apr-19 (20)
Recently uploaded
Recently uploaded (20)
Building on AWS Cloud One Codebase Aberdeen 25-apr-19
- 1. Building on AWS One Codebase Aberdeen 25-Apr-19 steve@cloudsoft.io
- 2. I want actionable insights I have a new business idea I have limited time and finite resources How did others succeed? How do I get started?
- 3. THINKING CHOOSING EXAMPLES STARTING
- 4. THINKING Greenfield or brownfield Pace layers Focus bullseye More resources
- 5. Greenfield or brownfield No legacy to migrate / retrofit No existing standards Freedom of choice Legacy launching board Existing standards foundation Default choices already available GO LIVE!
- 6. Pace layers
- 7. Focus bullseye EVERY STEP OUT FROM THE CENTRE COSTS $ EFFORT ^ 2 YOU $1 - Developing your applications $2 - Administering cloud services $4 - Building your own services $8 - Building your own platform
- 8. More resources https://blog.gardeviance.org/2015/03/on- pioneers-settlers-town-planners-and.html On Pioneers, Settlers, Town Planners and Theft (Wardley) https://www.wardleymaps.com/ Wardley Map / Value Chain (Wardley) https://itrevolution.com/book/accelerate/ Building & Scaling High Performing IT Orgs (Forsgren et al)
- 9. Use higher-order services Pick the right tool for the job Be Well-architected CHOOSING Case for / against microservices No undifferentiated heavy lifting
- 10. Higher order services DO Use Cloudformation or similar -as-code Use CI/CD managed release pipeline Use RDS managed database Use SQS & SNS glue for decoupling Carefully choose serverless/FaaS Use all the published best practices possible DON’T Click/configure via AWS console Let people log on to servers and make changes Use servers Think K8S/containers == 42 Build your own database server Build your own messaging system Build your own anything
- 11. No undifferentiated heavy lifting Build my own API gateway with nginx Use AWS API Gateway Build my own load balancer with nginx Use AWS Application Load Balancer Build my own message queue with RabbitMQ Use AWS Simple Queue Service Build my own MongoDB Use AWS DocumentDB Build my own relational database Use AWS RDS Build my own file server Use AWS EFS If it starts with “Build my own…” don’t do it.
- 12. Right tool for the job There are seven managed database services available on AWS - your app might use between one and seven of them at the same time. Relational Key-Value Document In-Memory Graph Time series Ledger https://aws.amazon.com/products/databases/ RDS DynamoDB DocumentDB Redis Neptune Timestream QLDB
- 14. The case for / against microservices https://dwmkerr.com/the-death-of-microservice-madness-in-2018/
- 15. Case Study Research EXAMPLES Startup Themes Online car valuation as-a-service
- 16. Case Study Research 170+ startup case studies https://aws.amazon.com/solutions/case- studies/startups/
- 17. Startup themes Violent scale Big data Access to technology Global reach Lean enterprise Batch processing Streams Security
- 18. Example: Car valuation as a service DVLA Insurance Finance Stream DatabaseS3 Application iOS Browser Buyer Dealer+WAF +CI/CD +DR 3rd PartyAPI On Cloud In Cloud
- 19. Begin with the end in mind Getting credits Cloud as Code Shared responsibility STARTING Find, Attract, Afford Retain - or Partner
- 20. Begin with the end in mind PRESS RELEASE ● Heading - Name the product in a way your target customers will understand. ● Sub-Heading - Market / Benefit ● Summary - Summary of the product and the benefit. ● Problem - What do you solve? ● Solution - How do you solve it elegantly? ● Quote from You - Spokesperson ● How to Get Started - Easy onboarding ● Customer Quote - hypothetical customer describing benefit ● Closing and Call to Action - Key takeaways and next steps FAQ ● How it works ● Pricing ● Where to get it ● How to get started ● Capture internal questions - don’t let them become internal tribal knowledge ● Capture market research / early prospect questions - if they ask, so will others KEEP IT SIMPLE - IT’S NOT A SPEC
- 21. Find, attract, afford, retain - or partner DIY STAFFING Talent in the tools/tech in your area vs. remote Do they want to work on your project? In your location? With you? Fully loaded cost of hiring is 2.5x-3x base salary Once they know your system: cost of churn? Only hire for core PARTNERING AWS is one kind of partner Pick topics in the inner ring of Bullseye Focus Don’t pick a partner that can’t understand your inner-circle captain competency Don’t pick a partners that wants you sell you people/services/things in the two outer circles Find a thinking partner that fits
- 23. Cloud as code Check out VisualComposer for AWS CloudFormation by Cloudsoft https://cloudsoft.io/composer
- 24. Shared responsibility - on cloud vs in cloud GOOD VIEW You focus on the app and delegate heavy lifting to partners and cloud. BAD VIEW You reinventing the wheel and doing undifferentiated heavy lifting. Treating AWS as old skool colo (IaaS) REALITY SOMEWHERE INBETWEEN