The document discusses how applying the principles of DevOps with Serverless impacts the teams that are built. It explains that DevOps is about flow, feedback and learning through people, processes and tools to deliver value. Serverless scales well, is resilient, secure and cheaper. The three ways of DevOps - flow, feedback and learning - can be achieved with Serverless by writing minimal code, deploying quickly, monitoring metrics, learning from failures and building resilient architectures. Following these principles results in teams that can build, deploy and monitor systems together effectively.

1. @_jonvines
Unleash your DevOps with
Serverless
How applying the principles of The Three Ways with Serverless impacts the teams we build

2. @_jonvines
DevOps is the principles of flow, feedback and
learning. It’s about the people, process and tools
needed to achieve outcomes and deliver value

3. @_jonvines

4. @_jonvines
why Serverless?
scales ● resilient ● secure ● cheaper

5. @_jonvines
can we do Serverless and DevOps at the same time?

6. @_jonvines
developer
/dɪˈvɛləpə/
noun
A person that writes code
operations
/ɒpəˈreɪʃ(ə)n/
noun
A person that manages and maintains your infrastructure

7. @_jonvines
principles of flow, feedback and learning

8. @_jonvines
i. the way of flow
moving from left (idea) to right (production)
as quickly as possible

9. @_jonvines
write as little code as possible
-
embraces infrastructure as code
-
enable systems thinking
-
bring reliability experiences to the team
-
build deployment and management tooling

10. @_jonvines
developer
/dɪˈvɛləpə/
noun
A person that builds systems writing as little code as possible
operations
/ɒpəˈreɪʃ(ə)n/
noun
A person that is responsible for the health of the teams services and systems as a whole and create deploy
and management tooling

11. @_jonvines
ii. the way of feedback
create and amplify fast and continuous feedback

12. @_jonvines
Instrument code for observability
-
include business metrics
-
make work visible

13. @_jonvines
developer
/dɪˈvɛləpə/
noun
A person that builds systems writing as little code as possible and instruments code created for observability
operations
/ɒpəˈreɪʃ(ə)n/
noun
A person that is responsible for the health of the teams services and systems as a whole, create deploy
and management tooling and ensures system and business metrics are visible

14. @_jonvines
iii. the way of learning
create opportunities for learning, as quickly,
frequently, cheaply and as soon as possible

15. @_jonvines
embrace scientific thinking
-
build resilient systems
-
redefine failure as opportunities to learn
-
define service templates

16. @_jonvines
developer
/dɪˈvɛləpə/
noun
A person that builds systems writing as little code as possible, instruments code created for observability, deploys
quickly to provide new learning opportunities and designing architectures that are resilient to failure
operations
/ɒpəˈreɪʃ(ə)n/
noun
A person that is responsible for the health of the teams services and systems as a whole, create deploy
and management tooling, ensures system and business metrics are visible and enables the team to adopt
resilient cloud architecture patterns

17. @_jonvines
developer
/dɪˈvɛləpə/
noun
A person that builds systems writing as little code as possible, instruments code created for observability, deploys
quickly to provide new learning opportunities and designing architectures that are resilient to failure
operations
/ɒpəˈreɪʃ(ə)n/
noun
A person that is responsible for the health of the teams services and systems as a whole, create deploy and
management tooling, ensures system and business metrics are visible and enables the team to adopt resilient
cloud architecture patterns

18. @_jonvines
team
/tiːm/
noun
1. builds systems writing as little code as possible, responsible for the health of the their services and systems as
a whole, create deploy and management tooling.
2. instruments code created for observability, ensures system and business metrics are visible
3. deploys quickly to provide new learning opportunities and designing architectures that are resilient to failure

19. @_jonvines
team
/tiːm/
noun
1. builds systems writing as little code as possible, responsible for the health of the their services and systems as
a whole, create deploy and management tooling.
2. instruments code created for observability, ensures system and business metrics are visible
3. deploys quickly to provide new learning opportunities and designing architectures that are resilient to failure

20. @_jonvines
we can do Serverless and DevOps at the same time!