Skip to content

Hello devops

mohamadreza bigdeli edited this page Feb 4, 2023 · 2 revisions

devops circle

devops engineers should implement CI/CD

plan > code > CI(build > test > release) > CD(deploy > operate) > monitor > feedback > plan > ...
  • plan: product owner team (tasks, responsibities,...)
  • code: developpers (generally microservice) (microservices in a monolithic model)
  • build: devops engineers should implement CI/CD (build docker image, deb, rpm, npm, go, ...)
  • test: devops engineers and devolopers
  • deploy: devops engineers (knowledge of different tools like DBs, message brokers,... )
  • operate: devops engineers (backup, restore, upgrade, downgrade, ...)
  • monitor: devops engineers (in order to predict disasters base on time series data. prometheus.)
  • feedback: we use all feedbacks(members, customers, developers, product manager, measurment test team, monitoring, logging, metrics, alerts, events,...) to designe new plan

requirements for impelimenting devops in an organization:

  1. agile: Agile is an iterative approach to project management and software development that helps teams deliver value to their customers faster and with fewer headaches. Instead of betting everything on a "big bang" launch, an agile team delivers work in small, but consumable, increments. Requirements, plans, and results are evaluated continuously so teams have a natural mechanism for responding to change quickly.
  2. lean culture: Lean culture is a type of company culture that focuses on continuous improvement, which refers to the optimization of an organization's protocols and processes regularly. When the members of a company embrace this concept, they can develop a collective commitment to learning and improving that focuses on the needs and expectations of customers.
  3. automation

Clone this wiki locally