What is the DevOps Radar?

The EVRY DevOps Radar is a list of technologies, complemented by an assessment result, called ring assignment. We use four rings with the following semantics:

• ADOPT — Technologies we have high confidence in to serve our purpose, also in large scale. Technologies with a usage culture in our EVRY production environment, low risk and recommended to be widely used across all segments.
• TRIAL — Technologies that we have seen work with success in project work to solve a real problem; first serious usage experience that confirm benefits and can uncover limitations. TRIAL technologies can be slightly more risky; some engineers in our organization may have walked this path and will share knowledge and experiences. Some of these tools are not recommended on general basis, but may serve as a sane choice when extra requirements are presented. E.g. some of these tools are geared towards the Enterprice market and may not be recommended for non-Enterprice.
• ASSESS — Technologies that are promising and have clear potential value-add for us; technologies worth to invest some research and prototyping efforts in to see if it has impact. ASSESS technologies have higher risks; they are often brand new and highly unproven in our organisation. You will find some engineers that have knowledge in the technology and promote it, you may even find teams that have started a prototyping effort. Requirements may wary so please have this in mind when doing an assessment of a tool.
• HOLD — Technologies not recommended to be used for new projects. Technologies that we think are not (yet) worth to (further) invest in. HOLD technologies should not be used for new projects, but usually can be continued for existing projects.

What is the purpose?

The DevOps Radar is a tool to inspire and support engineering teams at EVRY to pick the best technologies for new projects; it provides a platform to share knowledge and experience in technologies, to reflect on technology decisions and continuously evolve our technology landscape. Based on the pioneering work of ThoughtWorks, our DevOps Radar sets out the changes in technologies that are interesting in software development — changes that we think our engineering teams should pay attention to and consider using in their projects.

How do we maintain it?

The DevOps Radar is maintained by the EVRY DevOps Community — an open group of senior EVRY technologists committed to devote time to the Tech Radar purpose. The guild self organises to maintain the DevOps Radar documents, including this public version. Assignment of technologies to rings is the outcome of ring change proposals, which are discussed and voted on in guild meetings. The DevOps Radar depends on active participation and input from all engineering teams at EVRY.

This radar is based on the awesome work by Zalando and their open source Tech Radar to generate this visualization.