When you need to put a *ops in your Live

In the last years it has been appearing a lot of strategies about *ops in all the ecosystems of IT.

You can begin with DevOps, follow with FinOps and finish with ApiOps.

Now its time to put in order all this concepts and leave them in one place. And this posts is the Solution for the IT World ūüėČ

This is not a deeper analisis of every concept, only is the summary or description of every *Ops. If I will find more information or links I update the post only to have more knowledge about it.

The most important *Ops concepts:

ApiOps: APIOps applies the concepts of GitOps and DevOps to API deployment. By using practices from these two methodologies, APIOps can enable everyone involved in the lifecycle of API design, development, and deployment with self-service and automated tools to ensure the quality of the specifications and APIs that they’re building.

DevOps: Combination of software developers (dev) and operations (ops). It is defined as a software engineering methodology which aims to integrate the work of software development and software operations teams by facilitating a culture of collaboration and shared responsibility.

DevSecOps: DevSecOps stands for development, security, and operations. It’s an approach to culture, automation, and platform design that integrates security as a shared responsibility throughout the entire IT lifecycle.

FinOps: It’s the way for teams to manage their cloud costs, where everyone takes ownership of their cloud usage supported by a central best-practices group. Cross-functional teams in Engineering, Finance, Product, etc work together to enable faster product delivery, while at the same time gaining more financial control and predictability.

GitOps: The core idea of GitOps is having a Git repository that always contains declarative descriptions of the infrastructure currently desired in the production environment and an automated process to make the production environment match the described state in the repository. If you want to deploy a new application or update an existing one, you only need to update the repository Рthe automated process handles everything else. It’s like having cruise control for managing your applications in production.

DesignOps: DesignOps refers to the orchestration and optimization of people, processes, and craft in order to amplify design’s value and impact at scale.

ChatOps: ChatOps, sometimes known as conversation-driven collaboration or conversation-driven DevOps, is the use of chat clients, chatbots and other real-time communication tools to facilitate software development and IT operations tasks. GitHub is typically credited with originating the term ChatOps.

AIOps: Coined by Gartner, AIOps‚ÄĒi.e.¬†artificial intelligence for IT operations‚ÄĒis the application of¬†artificial intelligence (AI)¬†capabilities, such as natural language processing and machine learning models, to automate and streamline operational workflows.


Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

%d bloggers like this: