Each year, InfoQ editors discuss what we’ve been observing across the entire software development landscape, and create several trends reports, each with its own graph of the adoption curve. This helps the editorial team focus its reporting on innovative technologies and ideas, and also provides our readers with a high-level overview of topics to keep an eye on.

There are two major components of these reports. The first is the written report you are currently reading, and includes the trends graph and details on individual items that have been added or changed in the past year, as well a general analysis from the InfoQ editors.

The second part of the report is an episode of the InfoQ Podcast, which is a chance to listen in on part of the editors’ conversation and hear some anecdotal examples from our panel of expert practitioners.

Updates to the Trends Graph

In 2021, we looked at many ways architects shape their designs, considering major "-ilities." This year, we’ve added "design for security" to that list, and consider it at the early adopter stage. While security has always been a factor, it is increasingly important to consider security early and repeatedly when designing a system and its components.

Architecture may not be part of the portmanteau triplet DevSecOps, but it is an underlying component of that idea. There are also many similarities between cybersecurity and software architecture, as discussed with Maxime Lamothe-Brassard on the InfoQ Podcast.

We considered adding “design for scalability” but decided it was captured under the idea of “design for resilience” and other trends that exist to accommodate scalability. In the second year of the pandemic, consumption of online services continued to grow, and companies had to be able to scale to meet the demand.

eBPF, extended Berkley packet filters, are a way of programming the Linux kernel, and allowing developers a way of adding capabilities to the operating system at runtime. We’ve added eBPF as an innovator trend and will watch its adoption over the coming years. Liz Rice provided a great overview of the technology in a recent episode of the InfoQ Podcast.

The term "Next-gen GraphQL" was changed to GraphQL Federation, as it is the foremost aspect being adopted by companies building on top of their existing GraphQL implementations.

“Data gateways” was removed, and replaced with the “Data + Architecture.” Also, Architect Elevator was replaced with Architecture Decision Records. These changes are discussed in detail later in this report.

Both Dapr and WebAssembly have moved from Innovators to Early Adopters.

A couple of items were removed due to a lack of adoption and insufficient innovation being mentioned in the past few years. These were Open Application Model (OAM) and RSocket & Reactive Streams.