Key Software Architecture Trends for 2020: Micro Frontends, AsyncAPI, Data Mesh, Policy as Code, Serverless, Low‑Code, GraphQL and Ethics

Key Points

Emerging architecture trends to watch: micro frontends, data mesh, AsyncAPI, and Policy as Code, reflecting diverse innovation across the landscape.

As micro‑services become ubiquitous, many organizations are exploring how to correctly build distributed systems or modular monoliths before splitting into micro‑services.

GraphQL has clearly crossed the adoption gap, though its breadth of use in large enterprises continues to evolve.

Low‑code/no‑code platforms are gaining interest, enabling non‑developers to customize systems.

Concepts such as functional programming and event‑driven architecture are still niche and progress slowly.

Good software architecture helps manage complex systems. Recent innovations for distributed systems, event‑driven architecture, and big data aim to leverage emerging best practices and guide engineers away from common pitfalls.

InfoQ’s software architecture and design topic map highlights the current state of major architecture concepts in the industry, focusing on ideas that have moved from innovators to early adopters and those still awaiting broader acceptance.

Innovators

The four new trends identified among innovators are micro frontends, AsyncAPI, data mesh, and policy as code.

Micro Frontends

Micro frontends aim to bring the same benefits of micro‑services to the UI layer, allowing large applications to be broken into smaller, manageable pieces that can be developed and released independently.

After a discussion on the InfoQ podcast, Luca Mezzalira, author of *Building Micro Frontends*, shared his outlook for the next one‑to‑two years.

Micro frontends are not a brand‑new trend, but they gained traction in 2019. Many best practices are still emerging, and the community is very active. They are not a silver bullet for front‑end development, but they complement single‑page applications and server‑side rendering architectures. When dozens of developers work on a large business domain, micro frontends shine by reducing complexity through domain‑level partitioning and independent deployment. More case studies are expected in 2020 to illustrate benefits and trade‑offs. By 2020, micro frontends should become a mature pattern understood by the front‑end community, though not every project will need them.

AsyncAPI

AsyncAPI addresses the mismatch between RESTful APIs and event‑driven architectures, enabling a shift from synchronous request/response APIs to APIs built specifically for asynchronous communication.

Daniel Bryant noted that almost everyone adopting AsyncAPI/OpenAPI is looking for a solution like AsyncAPI.

Data Mesh

Zhamak Dehghani of ThoughtWorks introduced the data‑mesh concept, advocating domain‑oriented data ownership to avoid the pitfalls of traditional data warehouses or monolithic data pools.

Thomas Betts expressed interest in whether data mesh follows the trend of decomposing monolithic data into micro‑services for greater flexibility in big‑data systems.

Interconnected decentralization is a fundamental trend for the digital economy, and data mesh is a direct response to the failure of analytical data‑management models. In the next one‑to‑two years, broader adoption and more open‑source tooling are expected. Successful adoption requires organizational change around data ownership and strong executive support.

Policy as Code

Policy as Code extends the “infrastructure as code” mindset to the software‑development lifecycle, allowing desired system states to be expressed and enforced programmatically.

Early Adopters

Serverless

Serverless remains a debated topic; many believe it has not yet crossed the adoption gap and see it as a reaction against micro‑services, with only specific features like AWS Lambda achieving broader use.

Even a simple “Hello World” serverless app is highly distributed and requires skilled developers, raising questions about its cost‑effectiveness. Composite/structured design from the 1970s still applies to micro‑services.

Low‑Code / No‑Code

Low‑code/no‑code platforms promise to empower end‑users to build functionality without developer involvement, though some view them as vendor‑driven pushes.

Microsoft’s Power Platform and Google’s acquisition of AppSheet illustrate growing vendor interest. These platforms target non‑developers, shifting the challenge from building core systems to integration.

GraphQL

GraphQL has clearly crossed the adoption gap and is influencing architectural decisions around scalability and system cohesion.

Both Humble and Betts consider GraphQL to have moved from early adoption to mainstream, similar to TypeScript’s trajectory.

Ethics in Software Architecture

Bradley raised the question of tracking ethical standards within the architecture topic map; while ethics is often treated as a cultural issue, it remains a cross‑cutting concern that should continue to be monitored.

Humble believes ethics should be tracked as it impacts software’s pervasive role in society. Betts sees ethics as a responsibility of technical leaders, especially regarding regulations like GDPR and CCPA.

Other Topics

Reactive programming, HTTP/2, and gRPC have already crossed the gap, whereas many other ideas progress more slowly compared to programming‑language trends.

The remainder of the topic map stays largely unchanged, reflecting the longer maturation cycle of architectural concepts.