Cloud engineer’s journey and survival in the cloud

Talk for the AWS Abu Dhabi User Group Launch on Dec 8 at Abu Dhabi.

Super stoked to be given a chance to present here!

Transcript

1. WHAT it takes to be A Cloud Native Engineer ?
2. hello! I’m Ashwin! Director of Engg CoLearn - EdTech / Indonesia https://cruisemaniac.com | mail@cruisemaniac.com 2
3. ✘ Specialisation in scaling startup tech ✘ 4 Series-A to Series-B scale-ups ✘ Data center to pure cloud native ✘ Email, DNS servers 3
4. 0. Why are you here? 4
5. “ 5 I got invited to talk.. You???
6. “ Want to help your team see the benefits of being a cloud native org! Eng, Ops, Product & Business! 6
7. 1. Who is a Cloud Native Engineer ? 7
8. “ Someone with software, design and arch skills. 8
9. “ Has a tool box of specific skills and know-how to leverage cloud tech for the org. 9
10. 2. Let’s dig deeper... 10
11. DETAILS, FACTS, FIGURES Tools You’re an engineer. Always carry tools. Agility How quickly can you adapt to help deliver software? Culture Culture eats strategy for breakfast... 11
12. 3. Native vs. Agnostic 12
14. Software is an App. Infra is an App. You’re an App. Everything is an app! 14
15. Let the experts do the heavy lifting! Prepare for lockdown Time to market over Infra cost! Cloud Native Ahoy! Iteration velocity! Standardised App, Infra, O11y! Happy customer experience! 15
16. 4. Thinking Native! 16
17. Infra IS Code! DETAILS, FACTS, FIGURES Architecture IS sacrosanct! Velocity IS Key! 17
18. Infra Devs are from Venus, Ops are from Mars 18
19. Containers Lambdas Managed Services Monitoring Observability Releases 19
20. Arch No witty line here... 20
21. Distributed systems Event based interaction models Scale Resilience Microservices + Lambdas Statelessness 21
22. Velocity What color do you want that database? - Dilbert 22
23. Have a damn devil at work! 🦧 Pull plugs on systems - Prepare for failure state! Feature flagging if feature.enabled? actual feature code here Trunk based development $ git push -u origin master #OR GTFO! CI / CD - Go full or go home! Codepipeline Github workflows Jenkins users will be Disowned! Canary releases Roll on a friday evening Distributed tracing and logging Cloudwatch Newrelic Sentry 23
24. What should you get started on? 24
25. Operating Systems 25
26. Kernel management Process, I/O and Memory Management Threading, Concurrency, Race conditions Virtualization and Containerisation - cgroups File systems - Native + Distributed Computer Architecture 26
27. Networking 27
28. IPV4 / IPV6, CIDR Blocks, Network ranges, classes DNS Subnets, Addressing, Network Segmentation Routing, Network components - Gateways, VPNs Firewalls, security - TLS 1/1.1/1.2 WAN architectures - Load balancing, HA, Proxies, CDNs 28
29. Languages 29
30. Understand at least 2 programming languages Learn to write non-trivial code Understand how to deploy this code on a server - virtualbox / docker Understand databases at their algorithmic level. How does replication work? 30 Write non-trivial database scripts - PL/SQL / Stored Procedures
31. 5. Thinking Product! 31
32. Onboarding velocity Scalability Latency Hybrid models - deployment / pricing game Security and Compliance Monitoring As A Service 32
33. 6. Thinking Culture! 33
34. Independent arch. per pod! You build it! You own it! Simple is hard! Work together.. Prepare for shit storms! Simple is King! 34
35. Faster orgs will eat larger orgs with Shawarma and Kadak Chai! Embrace Change! Plan for unplanned work! Failure is the new normal.. Understand your devs.. Question your assumptions.. Question everyone’s assumptions.. 35
36. thanks! Any questions? You can find me at @cruisemaniac mail@cruisemaniac.com 36