Lifecycle of a microservices application - Iasi, Levi9 meetup - 28-6-2017

@PavelChunyayev
Lifecycle of a microservices application
What does it take to develop and run a micro service
by Pavel Chunyayev, 29-6-2017
Levi Nine, Iasi

@PavelChunyayev
In theory, there is no difference
between theory and practice.

@PavelChunyayev
In theory, there is no difference
between theory and practice.
But, in practice, there is.
Jan L.A. van de Snepscheut
and/or Yogi Berra

@PavelChunyayev
It may be all right in practice, but
it will never work in theory.
Warren Buffett

@PavelChunyayev
What we will cover today
• Lifecycles
• Process for application delivery
• Best team to develop a microservice
• Lean ideas

@PavelChunyayev
Pavel Chunyayev
• Already three years in the Netherlands
• Background in IT operations, Ukraine, Estonia
• Help software development to achieve
business goals
• In company with 900 smart engineers

@PavelChunyayev
Project lifecycle

@PavelChunyayev
Application lifecycle

@PavelChunyayev
Lifecycle of a feature
Plan Code Build Test Release OperateEnvision

@PavelChunyayev
Build
Measure
Learn

@PavelChunyayev
Build quality in
Shared responsibility

@PavelChunyayev
Continuous Delivery
Plan Code Build Test Release OperateEnvision

@PavelChunyayev
“Cease dependence on inspection to achieve quality. Eliminate the
need for inspection on a mass basis by building quality into the product
in the first place.”
W. Edwards Deming
Fourteen Points for the Transformation of Management

@PavelChunyayev
Build quality in
• Testing is not just presence or absence of defects
• Testing is not a separate process
• Test should not just raise the cost of maintenance
• Stop thinking about functional testing only
• Test early, move tests to the left
• Quality goal need to be established early in the development process
• Automated testing – part of Definition of Done
• TDD

@PavelChunyayev
Testing pyramid
Executiontime
Morebusinessfeedback
Moredevelopmentfeedback

@PavelChunyayev
Testing is a shared responsibility

@PavelChunyayev
Updating an API contract
Crucial monent in an application lifecycle

@PavelChunyayev
Updating the contract

@PavelChunyayev
A cross-functional team

@PavelChunyayev
High performing team – Purpose and Autonomy
• Does the mission/purpose of my company make me feel like my work
is important?
• Does my supervisor, or someone at work, seem to care about me as a
person?
• Do I understand how my everyday decision helps mission/purpose of
my company?
• Do I know what is expected of me at work?
• At work, do my opinions seem to count?

@PavelChunyayev
High performing team - Mastery
• Do I have the materials & equipment I need to do my work right?
• At work, do I have the opportunity to do what I do best every day?
• Is there someone at work who cares about my development?
• Are my co-workers committed to doing quality work?
• In the last 6 months, have I talked with someone about my
development?
• At work, have I had opportunities to learn and grow?

@PavelChunyayev
DoI have the opportunity to do
what I do best every day?

@PavelChunyayev
People are companies’ best asset

@PavelChunyayev
“Developing people and the system
so that together they are capable of
achieving successful results is the
point.”
Mary and Tom Poppendieck

@PavelChunyayev
Lean software development

@PavelChunyayev
Lean software development - Principles
• Eliminate waste
• Amplify learning
• Decide as late as possible
• Deliver as fast as possible
• Empower the team
• Build quality in
• Optimize for the whole

@PavelChunyayev
Waste
• Partially done work (Starting more than finishing)
• Extra processes (Bureaucracy)
• Extra features (Unnecessary code)
• Task switching (Changing requirements and priorities)
• Waiting (Delays in the development process)
• Motion
• Defects (Quality issues, rework)

@PavelChunyayev
Amplify learning
• Pair programming
• Code reviews
• Documentation
• Wiki
• Commented code
• Knowledge sharing sessions
• Training

@PavelChunyayev
Decide as late as possible
• For decisions that are irreversible or impractical to reverse
• Keep the options for as long as possible
• You will know a lot more by the time the decision needs to be made
• Too early and you are limited by the choice you could have made
without enough information

@PavelChunyayev
Deliver as fast as possible
• Continuous Delivery
• DevOps
• Agile methodologies
• Shared responsibility

@PavelChunyayev
Empower the people
• Give responsibility to make decisions about their work

@PavelChunyayev
Build quality in
• Andon – stop the line
• Pair programming
• Test driven development
• Constant feedback
• Minimize handovers (time between stages)
• Continuous integration
• Automation

@PavelChunyayev
Optimize for the whole
• Optimize for the whole, not specific departments or teams
• E2e process with focus on customer needs
• Prefer product orientation vs project orientation
• Focus on quality and innovation, not on quick execution

@PavelChunyayev
Problems of Lean
• Cargo cult
• Focus on tools, not on the philosophy and culture
• Decide on the solution without understanding true problem

@PavelChunyayev
+31 6 2117 5817
pavel@levi9.com
Common goal
Developer Product Owner Stakeholder

Lifecycle of a microservices application - Iasi, Levi9 meetup - 28-6-2017

Recomendados

Recomendados

Mais conteúdo relacionado

Mais procurados

Mais procurados (20)

Semelhante a Lifecycle of a microservices application - Iasi, Levi9 meetup - 28-6-2017

Semelhante a Lifecycle of a microservices application - Iasi, Levi9 meetup - 28-6-2017 (20)

Mais de Pavel Chunyayev

Mais de Pavel Chunyayev (8)

Último

Último (20)

Lifecycle of a microservices application - Iasi, Levi9 meetup - 28-6-2017

Notas do Editor