from devops to noops
TRANSCRIPT
![Page 1: From DevOps to NoOps](https://reader036.vdocuments.us/reader036/viewer/2022062902/58edd63d1a28ab44018b46ff/html5/thumbnails/1.jpg)
1
From DevOps to NoOpsLes FrostSenior Technical Architect - Capgemini
![Page 2: From DevOps to NoOps](https://reader036.vdocuments.us/reader036/viewer/2022062902/58edd63d1a28ab44018b46ff/html5/thumbnails/2.jpg)
2
Introductions
Les Frost Head of Technology Public Sector Digital and DevOps Unit http://linkedin.com/in/les-frost https://twitter.com/lesf99
Builds on a presentation by Graham Taylor Head of Platform Engineering Engineering Lead Applied Innovation Environment
London https://github.com/tayzlor https://twitter.com/g_taylor
![Page 3: From DevOps to NoOps](https://reader036.vdocuments.us/reader036/viewer/2022062902/58edd63d1a28ab44018b46ff/html5/thumbnails/3.jpg)
3
From DevOps to NoOps
• DevOps establishing itself within organisations. • Lots of questions about how to implement it• It’s not easy. It requires difficult cultural change• By the time organisations adopt DevOps will they be out of date? • Serverless computing outsources management of servers• Leaving you to focus on critical business functionality• Will this push organisations from DevOps to NoOps? • AWS Lambda and other serverless technologies lets you run code without
provisioning or managing servers.
![Page 4: From DevOps to NoOps](https://reader036.vdocuments.us/reader036/viewer/2022062902/58edd63d1a28ab44018b46ff/html5/thumbnails/4.jpg)
4
How many times have you been asked
"How do I do DevOps?"
"Can you tell me our recommended DevOps toolstack?“
"What do you think of this DevOps product?“
![Page 5: From DevOps to NoOps](https://reader036.vdocuments.us/reader036/viewer/2022062902/58edd63d1a28ab44018b46ff/html5/thumbnails/5.jpg)
5
The « DevOps » tools landscape..
![Page 6: From DevOps to NoOps](https://reader036.vdocuments.us/reader036/viewer/2022062902/58edd63d1a28ab44018b46ff/html5/thumbnails/6.jpg)
6
Organisations think they can buy DevOps in a box
![Page 7: From DevOps to NoOps](https://reader036.vdocuments.us/reader036/viewer/2022062902/58edd63d1a28ab44018b46ff/html5/thumbnails/7.jpg)
7
Will organisations make it in time?
By the time many enterprise organisations adopt "DevOps" they may already be out of date
![Page 8: From DevOps to NoOps](https://reader036.vdocuments.us/reader036/viewer/2022062902/58edd63d1a28ab44018b46ff/html5/thumbnails/8.jpg)
8
What if we’re too slow to market?
Disruption is everywhere and will affect all organisations
Shouldn’t we be focusing on critical business functionality?
![Page 9: From DevOps to NoOps](https://reader036.vdocuments.us/reader036/viewer/2022062902/58edd63d1a28ab44018b46ff/html5/thumbnails/9.jpg)
9
The problem with DevOps
...it makes the developer part of the operations team, and that can screech enterprise innovation and agility to a halt until it’s working well.
![Page 10: From DevOps to NoOps](https://reader036.vdocuments.us/reader036/viewer/2022062902/58edd63d1a28ab44018b46ff/html5/thumbnails/10.jpg)
10
The Dream
What if you could tell your IT organisation that their web app can have 99.99% availability and no servers that need to be patched or updated
or maintained.
Nothing to crash or get hacked or set off someone’s pager at 2am in the morning.
Instead, focus on the real problems you are solving and where you
provide value
![Page 11: From DevOps to NoOps](https://reader036.vdocuments.us/reader036/viewer/2022062902/58edd63d1a28ab44018b46ff/html5/thumbnails/11.jpg)
11
The Evolution of ArchitectureMonolith
![Page 12: From DevOps to NoOps](https://reader036.vdocuments.us/reader036/viewer/2022062902/58edd63d1a28ab44018b46ff/html5/thumbnails/12.jpg)
12
Micro-Services
![Page 13: From DevOps to NoOps](https://reader036.vdocuments.us/reader036/viewer/2022062902/58edd63d1a28ab44018b46ff/html5/thumbnails/13.jpg)
13
API Driven Development
![Page 14: From DevOps to NoOps](https://reader036.vdocuments.us/reader036/viewer/2022062902/58edd63d1a28ab44018b46ff/html5/thumbnails/14.jpg)
14
The evolution of compute and storagePhysical Servers and Discs
![Page 15: From DevOps to NoOps](https://reader036.vdocuments.us/reader036/viewer/2022062902/58edd63d1a28ab44018b46ff/html5/thumbnails/15.jpg)
15
Virtual Machines
![Page 16: From DevOps to NoOps](https://reader036.vdocuments.us/reader036/viewer/2022062902/58edd63d1a28ab44018b46ff/html5/thumbnails/16.jpg)
16
Containers
![Page 17: From DevOps to NoOps](https://reader036.vdocuments.us/reader036/viewer/2022062902/58edd63d1a28ab44018b46ff/html5/thumbnails/17.jpg)
17
Remember That Dream ?
![Page 18: From DevOps to NoOps](https://reader036.vdocuments.us/reader036/viewer/2022062902/58edd63d1a28ab44018b46ff/html5/thumbnails/18.jpg)
18
Serverless
Disclaimer: There are servers (you just don't need to worry about them)
It’s about standing on the shoulders of the tech giants (and cool startups).
![Page 19: From DevOps to NoOps](https://reader036.vdocuments.us/reader036/viewer/2022062902/58edd63d1a28ab44018b46ff/html5/thumbnails/19.jpg)
19
Serverless is about (micro) functionality
When you have an idea, it’s usually something like:“I want it to do this”
and you don’t usually say:“And I want it to be in this data centre, on these machines, with
this spec”
![Page 20: From DevOps to NoOps](https://reader036.vdocuments.us/reader036/viewer/2022062902/58edd63d1a28ab44018b46ff/html5/thumbnails/20.jpg)
20
Focus On
How to get more users, marketing, and the 20 million other things far more important to your business.
Real problems.
Your code. That's it.
![Page 21: From DevOps to NoOps](https://reader036.vdocuments.us/reader036/viewer/2022062902/58edd63d1a28ab44018b46ff/html5/thumbnails/21.jpg)
21
Care less about
• Managing uptime• Server maintenance• Upgrades• Security vulnerabilities
![Page 22: From DevOps to NoOps](https://reader036.vdocuments.us/reader036/viewer/2022062902/58edd63d1a28ab44018b46ff/html5/thumbnails/22.jpg)
22
Haven’t we seen this before?
If you've built a static website then you can call yourself a serverless hipster
![Page 23: From DevOps to NoOps](https://reader036.vdocuments.us/reader036/viewer/2022062902/58edd63d1a28ab44018b46ff/html5/thumbnails/23.jpg)
23
This isn't just about developers it’s also about cost
• With containers/virtualisation you have infrastructure running waiting to process requests
• If you are using auto scaling you still need a minimum infrastructure footprint and this costs money
• With serverless computing there aren’t any servers sitting there. The functionality is spun up in response to the request
• So you only get charged when your code actually running.
![Page 24: From DevOps to NoOps](https://reader036.vdocuments.us/reader036/viewer/2022062902/58edd63d1a28ab44018b46ff/html5/thumbnails/24.jpg)
24
Serverless unpacked
BaaS: Backend as a service FaaS: Function as a service
http://martinfowler.com/articles/serverless.html
![Page 25: From DevOps to NoOps](https://reader036.vdocuments.us/reader036/viewer/2022062902/58edd63d1a28ab44018b46ff/html5/thumbnails/25.jpg)
25
"Backend" services
![Page 26: From DevOps to NoOps](https://reader036.vdocuments.us/reader036/viewer/2022062902/58edd63d1a28ab44018b46ff/html5/thumbnails/26.jpg)
26
Function as a service
AWS Lambda lets you run code without provisioning or managing servers.
With Lambda, you can run code for virtually any type of application or backend service - all with zero administration.
Just upload your code and Lambda takes care of everything required to run and scale your code with high availability. You can set up your code to automatically trigger from other AWS services or call it directly from any web or mobile app.
![Page 27: From DevOps to NoOps](https://reader036.vdocuments.us/reader036/viewer/2022062902/58edd63d1a28ab44018b46ff/html5/thumbnails/27.jpg)
27
Function as a service
![Page 28: From DevOps to NoOps](https://reader036.vdocuments.us/reader036/viewer/2022062902/58edd63d1a28ab44018b46ff/html5/thumbnails/28.jpg)
28
Serverless Architecture
![Page 29: From DevOps to NoOps](https://reader036.vdocuments.us/reader036/viewer/2022062902/58edd63d1a28ab44018b46ff/html5/thumbnails/29.jpg)
29
Example 1: Web application
![Page 30: From DevOps to NoOps](https://reader036.vdocuments.us/reader036/viewer/2022062902/58edd63d1a28ab44018b46ff/html5/thumbnails/30.jpg)
30
Example 2 : Amazon Echo Hackathon
![Page 31: From DevOps to NoOps](https://reader036.vdocuments.us/reader036/viewer/2022062902/58edd63d1a28ab44018b46ff/html5/thumbnails/31.jpg)
31
The future comes with tradeoffs
• Less visibility• You can't fix it yourself, or add a feature• The service may protect itself at your expense• Shared limits
![Page 32: From DevOps to NoOps](https://reader036.vdocuments.us/reader036/viewer/2022062902/58edd63d1a28ab44018b46ff/html5/thumbnails/32.jpg)
32
Challenges
• End-to-end debugging• Monitoring• Tooling immaturity• Occasional latency issues• Patterns are still emerging
![Page 33: From DevOps to NoOps](https://reader036.vdocuments.us/reader036/viewer/2022062902/58edd63d1a28ab44018b46ff/html5/thumbnails/33.jpg)
33
Demo Time
Amazon Developer Console. Here’s we can see how we configure the Alexa voice service.https://developer.amazon.com/edw/home.html#/
Now let’s look at the AWS Lambda management console. This is where we define our serverless function.https://console.aws.amazon.com/lambda/home?region=us-east-1#/functions?display=list
If you want to see this working in real life you can follow it on Periscope or better still pop down to Conference room 3 on the ground floor to chat to the team.
![Page 34: From DevOps to NoOps](https://reader036.vdocuments.us/reader036/viewer/2022062902/58edd63d1a28ab44018b46ff/html5/thumbnails/34.jpg)
34
Conclusions
• Think carefully about costs and timescale of implementing DevOps
• It’s not easy and it will take a lot of time• Could this time and effort be better focused on critical
business functionality?• Serverless computing outsources management of servers• Leaving you to focus on critical business functionality• Will this push organisations from DevOps to NoOps?