middlewarebasert

Middleware-based, or middlewarebasert in Norwegian usage, describes an architectural approach in which software middleware acts as the core integration layer that coordinates communication, data exchange, and service orchestration among heterogeneous components and systems. The aim is to decouple applications from one another, enabling reuse and flexibility across platforms, languages, and protocols.

Key characteristics include decoupling of producers and consumers, abstraction of transport and integration logic, support for synchronous and asynchronous messaging, and centralized governance for security, logging, transactions, and error handling. Common middleware patterns include message-oriented middleware (MOM), enterprise service bus (ESB), API gateways, event streaming platforms, and integration platforms as a service (iPaaS).

In a middleware-based architecture, components interact through the middleware rather than direct calls, which reduces point-to-point dependencies but can introduce latency and operational complexity. It is often used to enable enterprise application integration, B2B messaging, data synchronization, and multi-channel customer experiences. It is complementary to, rather than a replacement for, microservices; microservices can leverage a middleware layer for cross-cutting concerns.

Historical note: middleware became prominent in the 1990s and 2000s with ESB and MOM technologies; more recently cloud-native and API-driven variants emphasize lightweight, scalable middleware, API management, and service meshes.

See also: middleware, ESB, MOM, API gateway, iPaaS, service mesh, SOA.