MASA (Mesh App and Service Architecture) has evolved from its 2017 introduction by Gartner into a foundational model for modern digital enterprises. It describes how to build a digital business as a connected mesh of apps, services, and APIs rather than as a set of monolithic applications.
MASA (Mesh App and Service Architecture) is a Gartner application architecture model in which apps are built as a mesh of independent apps, services, and APIs that span mobile, web, desktop, and IoT experiences. The goal is one connected digital business platform where each experience draws on shared backend services through well-defined APIs.
The model matters more now because APIs sit at the center of it. APIs make up more than half of the dynamic traffic on Cloudflare’s network, and automated discovery finds 30.7% more API endpoints than teams self-report, according to Cloudflare’s 2024 API Security and Management Report. On the infrastructure side, about 25% of organizations now run nearly all of their development and deployment cloud-native, per the CNCF Annual Survey 2024. MASA is the application-level pattern that ties those API-driven, cloud-native pieces together.
What is mesh app and service architecture?
Mesh app and service architecture is a model for building a digital business as an interconnected mesh of apps, services, and APIs rather than as monolithic applications. It forms the backbone of modern digital business technology platforms and lets a single solution deliver many experiences at once. At its core, MASA is a multidimensional model where applications exist as an interconnected mesh of independent and autonomous apps and services.
Three layers make up the mesh. Apps are the multichannel front ends across mobile, web, desktop, and IoT. Services are the backend business capabilities. APIs are the contracts that connect the two, so any app can consume any service in a governed way. A MASA application orchestrates a specific business process through several of these specialized services and apps rather than through one large codebase.
Because every connection runs through an API, API growth is a fair proxy for MASA adoption. Some 98% of enterprise decision-makers expect their number of APIs to increase over the next year, according to Axway’s 2024 API maturity research.
MASA vs service mesh, what is the difference?
MASA and a service mesh are different things that are easy to confuse because they share the word mesh. MASA is an application architecture model for the whole solution. A service mesh is an infrastructure layer inside an application that handles communication between services. They are complementary, and a service mesh can sit inside the backend of a MASA solution.
| Attribute | MASA (mesh app and service architecture) | Service mesh |
|---|---|---|
| What it is | An application architecture model for the whole digital solution | An infrastructure layer inside an application |
| Scope | Mobile, web, desktop, and IoT apps plus their backend services and APIs | Service-to-service communication among microservices |
| Main concern | Delivering one multi-experience solution across channels | Reliable, secure traffic with routing and observability |
| Building blocks | A mesh of apps, services, APIs, and events | A data plane of sidecar proxies and a control plane |
| Example technology | APIs, microservices, serverless, containers, API management | Istio, Linkerd, Consul |
| Origin | Gartner, 2017 | Cloud-native community |
In short, MASA answers how a whole digital business is structured across channels, and a service mesh answers how the microservices inside it talk to each other. You can adopt MASA without a service mesh, and you can run a service mesh in an architecture that is not MASA.
How MASA relates to monolithic and microservices architecture
MASA evolves the ideas behind service-oriented architecture and microservices. A monolithic application packages every function into one deployable unit, which is simple at first but hard to scale and change. Service-oriented architecture broke that monolith into coarse services. Microservices went further, into small, independently deployable services, and a service mesh often manages the traffic between them.
MASA sits one level up. It assumes microservices and APIs exist, then organizes them into a mesh that serves many front-end experiences at once. The three-tier web model puts a single web front end in front of one application tier and one database. That is no longer enough when the same business capability must reach a phone app, a browser, a partner system, and an IoT device, so MASA is the pattern for that many-to-many reality.
Core capabilities and requirements of a MASA implementation
A workable MASA implementation depends on a few capabilities. Modern implementations typically need three: service discovery and integration, API product management, and ecosystem enablement so internal teams, partners, and external developers can all build on the mesh.
Alongside those capabilities, most teams adopt five requirements:
- Cloud-native architecture. Applications use cloud-native patterns and technologies such as containers and Kubernetes.
- Edge-enabled. Solutions process data and deliver services at the network edge. Global edge-computing spending is on track to grow from about $261 billion in 2025 to $380 billion by 2028, according to IDC figures reported by Computer Weekly.
- API-first design. Every capability is exposed through an API so any app can consume it.
- Product-centric approach. APIs are treated as products with clear business value, owners, and lifecycles.
- Observable. Distributed tracing, metrics, and logs make the mesh possible to run and debug.
Security belongs in every layer, not at the end. In the past year, 99% of organizations experienced API security issues, according to Salt Security’s State of API Security. A MASA mesh therefore needs authentication, authorization, and monitoring on every API. AI is now part of the toolchain too. Some 84% of developers use or plan to use AI tools, up from 76% a year earlier, per the Stack Overflow 2025 Developer Survey. That raises the value of consistent, well-governed APIs that AI agents can call safely.
We now live and work in a very distributed environment, and we need flexibility and adaptability in the tools we use. Developers need a more cohesive experience.
Vince Padua, Chief Product Officer at Axway
Implementing MASA with API management and marketplaces
MASA provides the architectural blueprint, but a blueprint is not a running system. Turning the mesh into a working digital business needs a platform that can discover, secure, and manage APIs across distributed environments while making them consumable as products. This is where API management with marketplace capabilities does the practical work of MASA.
The gap is real. Some 78% of decision-makers do not know how many APIs they have, according to Axway’s 2024 API governance research, and 74% say more than a fifth of their APIs are unmanaged, per the same survey. A mesh of services only delivers value when those services can be found, trusted, and reused, which is a governance and marketplace problem as much as an architecture one.
Axway’s Amplify Platform supports this with federated API management that works across multiple vendors, deployment models, and API styles. With Amplify Engage, teams turn a MASA implementation into business value by enabling API discovery, adoption, and revenue while keeping governance and security across the ecosystem. Treating architecture (MASA) and API management as distinct but complementary concerns is what lets the mesh scale.
Decision-makers are beginning to grasp how APIs transform their business. Download the State of Enterprise API Maturity report to see the data.
Frequently Asked Questions
What is MASA (Mesh App and Service Architecture)?
MASA (Mesh App and Service Architecture) is a Gartner application architecture model where a digital solution is built as a mesh of independent apps, services, and APIs spanning mobile, web, desktop, and IoT. Gartner introduced it in 2017.
What is the difference between MASA and a service mesh?
MASA and a service mesh are different. MASA is an application architecture model for the whole solution across channels, while a service mesh is an infrastructure layer that manages communication between microservices. A service mesh can run inside a MASA backend.
How is MASA related to microservices?
Microservices are one of MASA’s building blocks. MASA assumes small, independently deployable services and APIs already exist, then organizes them into a mesh that serves many front-end experiences at once.
What is a device mesh in MASA?
The device mesh is the set of endpoints people use to reach digital services, including mobile, web, desktop, wearables, and IoT devices. MASA is designed so one set of backend services and APIs can serve all of them.
How does MASA relate to SOA and the three-tier model?
MASA evolves service-oriented architecture and moves past the three-tier web model. Instead of one front end talking to one application tier and one database, MASA connects many channels to shared services through APIs.
What are the core requirements of a MASA implementation?
A MASA implementation is typically cloud-native, edge-enabled, API-first, product-centric, and observable, and it relies on service discovery, API product management, and API management with marketplace capabilities.
Is MASA still relevant in 2026?
Yes. MASA is still relevant because its core idea, connecting many experiences through shared services and APIs, matches how cloud-native, API-first, and AI-driven applications are built today, even as the terminology has broadened.