Layered Thinking and Layered Models in Architecture Design

Architecture Thinking Overview

Architecture thinking combines system, structured, and programming mindsets, acting as a bridge between business reality and IT implementation. Its core is business‑driven technology, balancing requirements, implementation, cost, and benefit.

Decomposition and Integration

Decomposition breaks complex problems into cohesive, loosely‑coupled parts, requiring clear requirements. Integration reassembles components via appropriate interfaces; without integration, decomposition is meaningless.

Layered Thinking in Architecture

Layered architecture clarifies system understanding. A common cloud three‑layer model (IaaS, PaaS, SaaS) maps to resource, platform, and application layers. A service layer often sits between platform and application to decouple resources and services.

SOA Layering: Component‑Service‑Process

SOA emphasizes a distinct service layer, separating resources, services, and applications. Typical SOA diagrams show component, service domain, and process layers.

Fusion of Cloud and SOA Layers

Combining cloud and SOA yields a unified model where each cloud layer can be further split into resource, service, and application sub‑layers, supporting both technical and business perspectives.

Application Architecture Layers

Classic three‑tier architecture consists of UI, business logic (domain), and data access layers, optionally adding façade, API, or DTO layers. Domain‑driven design introduces an application layer and renames business logic to domain layer and data access to infrastructure layer.

Software Technical Architecture

Technical architecture mirrors the three‑tier model, detailing key technologies or products per layer (e.g., messaging middleware like RabbitMQ). It focuses on technology choices rather than business functions.

Overall Layered Diagram Logic

When drawing comprehensive architecture diagrams, place standards (security, quality, etc.) on the sides and the layered core (resource, platform, service, application) in the center, ensuring a consistent perspective across cloud, SOA, and application views.