Intro to devops
Culture, values and tools
Sergio Flores
Software Engineer
sflores@ecaresoft.com.mx
What is devops?
DevOps is the practice of operations and development engineers participating
together in the entire service lifecycle, from design through the development
process to production support.
AGILE CULTURE
OPS
DEVELOPMENT
AUTOMATION
TOOLS
QUALITY
ASSURANCE
Devops lifecycle
Agile Manifesto
DevOps Journey,by Mirco Hering
Architectural changes
★ We need to be able to deploy small
changes often.
★ We need to be able to have great
confidence in the quality of our
changes.
Architecture rules of thumb
- Separation of concerns:
we should consider different aspects of a system separately.
Coupling: Refers to the degree of dependency
between two modules.
We always want low coupling between modules.
- High cohesion:
Cohesion can be used as a measure of how strongly
related the functions in a module are.
Microservices
Everything is code
• The applications that we build
• The infrastructure that hosts our applications (IaC)
• The documentation that documents our products
An agile git flow:
Atlassian workflow for CI/CD
Git flow by Vincent Driessen
Continuous Integration
What is continuous integration?
Practice of routinely integrating code changes into
the main branch of a repository, and testing the
changes, as early and often as possible. Ideally,
developers will integrate their code daily, if not
multiple times a day.
Continuous delivery
What is continuous delivery?
the ability to get changes of all types—including new features, configuration
changes, bug fixes and experiments—into production, or into the hands of users,
safely and quickly in a sustainable way.
The importance of culture
Rogers Adoption Curve
Devops at ecaresoft
Lecturas recomendadas
An intro to devops: culture, values and tools

An intro to devops: culture, values and tools

  • 1.
    Intro to devops Culture,values and tools Sergio Flores Software Engineer sflores@ecaresoft.com.mx
  • 3.
    What is devops? DevOpsis the practice of operations and development engineers participating together in the entire service lifecycle, from design through the development process to production support. AGILE CULTURE OPS DEVELOPMENT AUTOMATION TOOLS QUALITY ASSURANCE
  • 4.
  • 5.
  • 7.
  • 8.
    Architectural changes ★ Weneed to be able to deploy small changes often. ★ We need to be able to have great confidence in the quality of our changes.
  • 9.
    Architecture rules ofthumb - Separation of concerns: we should consider different aspects of a system separately.
  • 10.
    Coupling: Refers tothe degree of dependency between two modules. We always want low coupling between modules. - High cohesion: Cohesion can be used as a measure of how strongly related the functions in a module are.
  • 11.
  • 12.
    Everything is code •The applications that we build • The infrastructure that hosts our applications (IaC) • The documentation that documents our products
  • 13.
    An agile gitflow: Atlassian workflow for CI/CD Git flow by Vincent Driessen
  • 14.
    Continuous Integration What iscontinuous integration? Practice of routinely integrating code changes into the main branch of a repository, and testing the changes, as early and often as possible. Ideally, developers will integrate their code daily, if not multiple times a day.
  • 15.
    Continuous delivery What iscontinuous delivery? the ability to get changes of all types—including new features, configuration changes, bug fixes and experiments—into production, or into the hands of users, safely and quickly in a sustainable way.
  • 17.
  • 18.
  • 19.
  • 20.