Over the past three weeks, I’ve been building a DevOps knowledge platform for all sorts of reasons.

GitHub:github.com/phodal/ledg…

Online use: devops.phodal.com/

In this knowledge platform, it includes the following:

  • DevOps tool periodic table. Help you select DevOps tools for the digital age.

  • DevOps design tools. Helps you design DevOps processes within your organization, covering processes, people, tools, artifacts, and more.

  • Case study. From the community’s knowledge base, we’ve distilled the experience of traditional enterprises moving towards DevOps into easy-to-use content and materials.

  • Best practices. We’ve distilled a number of best practices from the vast amount of DevOps content to help organizations better engage in DevOps practices.

  • Patterns and principles. Based on our practice, we have distilled the patterns and principles behind it to help individuals and organizations better understand the DevOps culture.

  • Operation manual. Practice and principles alone won’t get small to medium SIZED IT teams to make the DevOps transition, so we’ve prepared a thorough how-to manual to help you move forward.

  • Measurements. Kpi-metrics, measures-KPIs, KPI-metrics to help you better measure the DevOps transformation.

  • The report. We tried to extract useful practices and tools from the rich DevOps reports.

  • Mobile enterprise. We believe DevOps improvement in mobile applications is the challenge for most companies.

  • Tool. Tools, tools, tools are the best productivity, tools are more reliable than a person’s memory.

At first, I wanted to make some DevOps tools, such as the “DevOps Periodic Table” for China. By the way, I didn’t invent this tool, I just implemented it with a better architecture. This way, for most developers, he or she can assemble molecules from the table that fit their organization (the periodic table is all atoms, after all). A few days later, I had a tool that, based on each step of the development system, you could pick and choose what was right for you:

DevOps periodic table

To fill out the above elements, I had to look at case after case of big companies to see what technology stack they were using. So, I’ve pieced it together, and by the way, since I have examples of big companies, why don’t I abstract them. So here it is:

Case study

We’ve pulled examples of major companies from various parts of the Internet (see sources in the content) :

  • tencent

  • millet

  • China merchants bank,

  • Meituan

  • …

These cases often contain and hide various value orientations. So, further, I want to extract these patterns, so here it is:

Patterns and Principles

Contains:

  • Fluency mode

  • Measurement system design

  • Construction of learning organization

  • …

With these packages drawn, we can then move into the Design and implementation phase of DevOps. We need to find the best practices: programming, teams, culture, capabilities, testing, etc. :

practice

Too much, don’t write. Of course, in order to implement DevOps in your organization, we also need a manual to help you build a DevOps system step by step:

From measurement, to practice, to engineering, and then to get through the process, follow the trend, step by step practice.

tool

It’s not enough to just have a manual, but we’ve also made a variety of tools: besides the name of the tool, it also includes:

  • Preparations for tools

  • This section describes how to operate tools

  • Examples of tools

  • The tool is an online tool to use

There are more features in development. Also welcome to join our development team, more cases will help everyone grow better.

GitHub:github.com/phodal/ledg… Online use: devops.phodal.com/