Slide 1
Slide 1 text
WHAT it takes to be
A Cloud Native
Engineer ?
Slide 2
Slide 2 text
hello!
I’m Ashwin!
Director of Engg
CoLearn - EdTech / Indonesia
https://cruisemaniac.com | [email protected]
2
Slide 3
Slide 3 text
✘ Specialisation in scaling startup tech
✘ 4 Series-A to Series-B scale-ups
✘ Data center to pure cloud native
✘ Email, DNS servers
3
Slide 4
Slide 4 text
0.
Why are you here?
4
Slide 5
Slide 5 text
“
5
I got invited to talk..
You???
Slide 6
Slide 6 text
“
Want to help your team see the
benefits of being a cloud native
org!
Eng, Ops, Product & Business!
6
Slide 7
Slide 7 text
1.
Who is a
Cloud Native Engineer ?
7
Slide 8
Slide 8 text
“
Someone with software, design
and arch skills.
8
Slide 9
Slide 9 text
“
Has a tool box of specific skills
and know-how to leverage cloud
tech for the org.
9
Slide 10
Slide 10 text
2.
Let’s dig deeper...
10
Slide 11
Slide 11 text
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
Slide 12
Slide 12 text
3.
Native vs. Agnostic
12
Slide 13
Slide 13 text
13
Slide 14
Slide 14 text
Software is an App. Infra is an App. You’re an
App. Everything is an app!
14
Slide 15
Slide 15 text
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
Slide 16
Slide 16 text
4.
Thinking Native!
16
Slide 17
Slide 17 text
Infra IS Code!
DETAILS, FACTS, FIGURES
Architecture IS sacrosanct! Velocity IS Key!
17
Slide 18
Slide 18 text
Infra
Devs are from Venus, Ops are from Mars
18
Slide 19
Slide 19 text
Containers Lambdas Managed Services
Monitoring Observability Releases
19
Slide 20
Slide 20 text
Arch
No witty line here...
20
Slide 21
Slide 21 text
Distributed systems Event based interaction
models
Scale
Resilience Microservices + Lambdas Statelessness
21
Slide 22
Slide 22 text
Velocity
What color do you want that database?
- Dilbert
22
Slide 23
Slide 23 text
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
Slide 24
Slide 24 text
What should you get
started on?
24
Slide 25
Slide 25 text
Operating Systems
25
Slide 26
Slide 26 text
Kernel management Process, I/O and Memory
Management
Threading, Concurrency, Race
conditions
Virtualization and Containerisation -
cgroups
File systems - Native +
Distributed
Computer Architecture
26
Slide 27
Slide 27 text
Networking
27
Slide 28
Slide 28 text
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
Slide 29
Slide 29 text
Languages
29
Slide 30
Slide 30 text
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
Slide 31
Slide 31 text
5.
Thinking Product!
31
Slide 32
Slide 32 text
Onboarding velocity Scalability Latency
Hybrid models - deployment /
pricing game
Security and Compliance Monitoring As A Service
32
Slide 33
Slide 33 text
6.
Thinking Culture!
33
Slide 34
Slide 34 text
Independent arch. per pod! You build it! You own it! Simple is hard!
Work together.. Prepare for shit storms! Simple is King!
34
Slide 35
Slide 35 text
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