Ops is the past! DevOps is the present ! SRE is for giants! NoOps is the future! Fowler even says that a DevOps Engineer is an anti-pattern!
So will our job disappear in 10 years? What can we do about it? What is the next set of skills that we need? A startup is often a precursor to larger changes. I'll tell you what we are trying to do at Curve, a Fintech startup where developers build Kubernetes clusters and the SRE team codes microservices.
23. Platform engineering
Distributed systems concerns :
- Circuit breaking
- Retrying, Caching
- System monitoring
- Graceful degradation
- Rate limiting
Compliance.
Separation of concerns and duties.
NoOps:
Developers should not worry about
where the code will be deployed, or
where to test it !
Capacity Sizing
Load testing
Know your SaaS !
To worry about the platform, rather than the infrastructure...
24. Guided ownership
Developers on-call Monitoring
services
Chatbots
Floating engineer
Operational
training
Postmortems
over runbooks
SSH on production
nodes
25. Me & my code
Collaborate in
choosing a DB
engine and the
libraries
You can’t afford to
stay away from the
code
Code in the library
you chose
Own one or more
microservices:
QAutomator
26. Business value
Create dashboards,
presentations
Make procedures as
simple as possible
There is ZERO business value in :
updating nginx to 1.12.1
There is a business value of 4 million pounds in preventing
data leaks because of a bug in nginx 1.12.0, according to GDPR.
Reduce development
feedback loop
Don’t be scared
of talking money
27. The real anti-patterns :
“I code in Python but I’m not a developer”
Learning Terraform instead of Infra as
Code
Control instead of collaboration
Defining SLAs instead of user churn rate