GRAPH NAME APPLICATION ARCHITECTURE - FROM MONOLITHS TO DISTRIBUTED APPLICATIONS *** ## NODE 1 NAME BATCH APPLICATION ARCHITECTURE DATE 1950 PLACE USA AND EUROPE WHO EARLY COMPUTER PROGRAMMING COMMUNITY BRIEF DESCRIPTION Early computer applications are commonly organized as single programs that receive a prepared input, execute a sequence of calculations, and generate output. User interface, processing logic, data access, and execution control are usually tightly coupled inside one program. This batch-oriented monolithic architecture represents the starting point from which later application components are progressively separated. LINK *** ## NODE 2 NAME SUBROUTINE-BASED APPLICATION DECOMPOSITION DATE 1951 PLACE United Kingdom - England - Cambridge WHO David Wheeler, Maurice Wilkes and EDSAC community BRIEF DESCRIPTION Reusable subroutines demonstrate that application behavior can be decomposed into independently callable procedures rather than written as one continuous sequence of instructions. Application architecture begins acquiring internal structure through named computational components connected by call-and-return relationships. LINK *** ## NODE 3 NAME INTERACTIVE TIME-SHARING APPLICATIONS DATE 1961 PLACE USA - Massachusetts - Cambridge WHO Fernando Corbató and MIT BRIEF DESCRIPTION CTSS demonstrates interactive applications operating within independent user sessions on a shared computer. Applications are no longer exclusively offline batch jobs. Persistent users, terminals, files, processes, command interpreters, access control, and shared services become architectural concerns. LINK *** ## NODE 4 NAME LAYERED SYSTEM ARCHITECTURE DATE 1968 PLACE Netherlands - Eindhoven WHO Edsger W. Dijkstra and Technological University Eindhoven BRIEF DESCRIPTION The THE multiprogramming system demonstrates hierarchical organization in which system functions are divided into ordered layers of abstraction. Higher levels rely on services implemented below them while lower levels remain independent of higher-level details. Layering becomes one of the most influential principles for structuring applications and operating systems. LINK *** ## NODE 5 NAME UNIX PROCESS ARCHITECTURE DATE 1969 PLACE USA - New Jersey - Bell Laboratories WHO Ken Thompson, Dennis Ritchie and collaborators BRIEF DESCRIPTION Unix develops an application environment centered on independent processes, files, standard streams, and small utilities. Instead of assuming that every application capability belongs inside one executable, functionality can be separated into programs with narrow responsibilities. LINK *** ## NODE 6 NAME UNIX PIPE AND FILTER ARCHITECTURE DATE 1973 PLACE USA - New Jersey - Bell Laboratories WHO Douglas McIlroy, Ken Thompson and UNIX team BRIEF DESCRIPTION Unix pipes allow the output of one application component to become the input of another. The pipe-and-filter style demonstrates that complex application behavior can emerge through composition of independent processing stages connected through standardized data streams. LINK *** ## NODE 7 NAME COMMAND-LINE APPLICATION INTERFACE DATE 1973 PLACE USA WHO UNIX COMMUNITY BRIEF DESCRIPTION Unix establishes the command-line program as a reusable application component with arguments, standard input, standard output, exit status, and composability with other commands. The CLI becomes a durable application interface for users, scripts, automation, operations, build systems, and administrative tools. LINK *** ## NODE 8 NAME CRON SCHEDULER DATE 1975 PLACE USA - New Jersey - Bell Laboratories WHO UNIX COMMUNITY BRIEF DESCRIPTION Unix cron establishes a general mechanism for executing commands and applications according to schedules. Time-based execution becomes separable from the application itself. The scheduler evolves into a distinct architectural component found in operating systems, enterprise applications, distributed job systems, cloud platforms, and workflow engines. LINK *** ## NODE 9 NAME MODEL VIEW CONTROLLER DATE 1979-12-10 PLACE USA - California - Palo Alto WHO Trygve Reenskaug and XEROX PARC BRIEF DESCRIPTION Model-View-Controller explicitly separates domain information, presentation, and user interaction. The architecture demonstrates that application user interfaces should not require business state and interaction logic to exist in one tightly coupled component. Controller, model, and view become enduring architectural roles. LINK *** ## NODE 10 NAME SMALLTALK APPLICATION ENVIRONMENT DATE 1980 PLACE USA - California - Palo Alto WHO XEROX PARC BRIEF DESCRIPTION Smalltalk-80 provides an integrated object-oriented application environment built around interacting objects, graphical views, controllers, reusable classes, and event-driven behavior. Application structure increasingly becomes a network of collaborating components rather than a single procedural control flow. LINK *** ## NODE 11 NAME CLIENT-SERVER APPLICATION ARCHITECTURE DATE 1980 PLACE GLOBAL WHO NETWORKED COMPUTING COMMUNITY BRIEF DESCRIPTION As personal workstations and local networks spread, applications increasingly divide responsibilities between client programs interacting with users and remote servers providing shared data or computational services. The client-server model establishes one of the most important architectural boundaries in application history. LINK *** ## NODE 12 NAME REMOTE PROCEDURE CALL DATE 1984 PLACE USA - California - Palo Alto WHO Andrew Birrell and Bruce Nelson BRIEF DESCRIPTION Remote Procedure Call formalizes a programming abstraction in which one application component can invoke functionality running in another process or machine. Client and server stubs, serialization, request-response communication, and interface contracts become reusable architectural infrastructure. LINK *** ## NODE 13 NAME NETWORK FILE SERVICE ARCHITECTURE DATE 1984 PLACE USA - California WHO SUN MICROSYSTEMS BRIEF DESCRIPTION Network File System allows applications to use remote persistent resources through filesystem-like interfaces. Application components can rely on services hosted elsewhere without embedding the remote storage implementation directly into application logic. LINK *** ## NODE 14 NAME ERLANG SUPERVISED APPLICATIONS DATE 1986 PLACE Sweden WHO Joe Armstrong, Robert Virding, Mike Williams and ERICSSON BRIEF DESCRIPTION Erlang develops an application architecture based on lightweight processes exchanging messages. Failure isolation and supervision are treated as normal application concerns. Components can fail independently and supervisors can restart them, anticipating resilient service and worker architectures. LINK *** ## NODE 15 NAME WORLD WIDE WEB CLIENT-SERVER MODEL DATE 1989-03 PLACE Switzerland - Geneva WHO Tim Berners-Lee and CERN BRIEF DESCRIPTION The World Wide Web proposal defines a globally distributed information architecture in which clients request addressable resources from servers. The browser and Web server later become dominant frontend and backend application components connected through standardized protocols. LINK *** ## NODE 16 NAME PUBLIC WEB APPLICATION PLATFORM DATE 1991-08-06 PLACE Switzerland - Geneva WHO Tim Berners-Lee and CERN BRIEF DESCRIPTION The World Wide Web becomes publicly accessible as a universal application delivery environment. HTML documents provide presentation, URLs provide resource identity, HTTP provides communication, browsers provide clients, and Web servers provide remotely deployable backends. LINK *** ## NODE 17 NAME CORBA DISTRIBUTED OBJECT ARCHITECTURE DATE 1991 PLACE GLOBAL WHO OBJECT MANAGEMENT GROUP BRIEF DESCRIPTION CORBA standardizes distributed object invocation through an Object Request Broker and Interface Definition Language. Application components written in different languages and hosted on different machines can interact through formal remote interfaces, establishing an influential middleware architecture. LINK *** ## NODE 18 NAME COMMON GATEWAY INTERFACE DATE 1993 PLACE USA - Illinois - NCSA WHO NCSA WEB SERVER COMMUNITY BRIEF DESCRIPTION The Common Gateway Interface allows Web servers to execute external programs in response to HTTP requests. The Web changes from primarily serving static documents to executing backend application logic dynamically. CGI establishes one of the earliest standardized boundaries between a Web server and application code. LINK *** ## NODE 19 NAME DYNAMIC WEB BACKEND DATE 1993 PLACE GLOBAL WHO WEB DEVELOPMENT COMMUNITY BRIEF DESCRIPTION CGI programs, database access, generated HTML, and HTTP forms establish the dynamic Web application. A browser acts as frontend, an HTTP server accepts requests, backend programs perform application logic, and persistent systems provide data. The recognizable modern Web application stack begins to emerge. LINK *** ## NODE 20 NAME DESIGN PATTERNS DATE 1994 PLACE GLOBAL WHO Erich Gamma, Richard Helm, Ralph Johnson and John Vlissides BRIEF DESCRIPTION Design Patterns documents reusable structures for object-oriented software including Observer, Command, Strategy, Adapter, Factory, Proxy, Decorator, and other collaboration patterns. Application architecture gains a standardized vocabulary for recurring internal component relationships. LINK *** ## NODE 21 NAME JAVASCRIPT DATE 1995 PLACE USA - California WHO Brendan Eich and NETSCAPE BRIEF DESCRIPTION JavaScript brings executable application logic into the Web browser. The frontend evolves from a mostly passive document renderer into a programmable application environment capable of validation, event handling, state manipulation, asynchronous communication, and eventually complete application execution. LINK *** ## NODE 22 NAME THREE-TIER APPLICATION ARCHITECTURE DATE 1995 PLACE GLOBAL WHO ENTERPRISE SOFTWARE COMMUNITY BRIEF DESCRIPTION Enterprise applications increasingly separate presentation, application or business logic, and data persistence into distinct tiers. The three-tier structure creates clearer operational and responsibility boundaries between frontend systems, backend application servers, and databases. LINK *** ## NODE 23 NAME JAVA SERVLET ARCHITECTURE DATE 1997 PLACE USA - California WHO SUN MICROSYSTEMS BRIEF DESCRIPTION Java Servlets provide a persistent server-side component model for processing Web requests inside a managed application server. Unlike CGI processes created for individual requests, servlet containers can maintain reusable application components, lifecycle management, sessions, and shared services. LINK *** ## NODE 24 NAME FRONT CONTROLLER ARCHITECTURE DATE 1997 PLACE GLOBAL WHO WEB APPLICATION COMMUNITY BRIEF DESCRIPTION Web frameworks increasingly route incoming requests through a central application component before invoking specific business behavior. The Front Controller consolidates routing, authentication, logging, error handling, and request processing and becomes an ancestor of modern Web routers and API controllers. LINK *** ## NODE 25 NAME ENTERPRISE APPLICATION SERVER DATE 1999 PLACE GLOBAL WHO SUN MICROSYSTEMS AND JAVA ENTERPRISE COMMUNITY BRIEF DESCRIPTION J2EE establishes a standardized enterprise application environment containing Web components, business components, transactions, security, messaging, naming, persistence integration, and deployment descriptors. Application servers become managed containers for backend application components. LINK *** ## NODE 26 NAME SERVICE-ORIENTED ARCHITECTURE DATE 1999 PLACE GLOBAL WHO ENTERPRISE INTEGRATION COMMUNITY BRIEF DESCRIPTION Service-oriented architecture emerges as a way to organize enterprise capabilities behind network-accessible service contracts. Applications increasingly consume functionality from separately managed services rather than incorporating every capability into one process or codebase. LINK *** ## NODE 27 NAME REST ARCHITECTURAL STYLE DATE 2000 PLACE USA - California - Irvine WHO Roy Fielding BRIEF DESCRIPTION REST formalizes an architectural style for network-based applications centered on resources, representations, stateless interactions, uniform interfaces, caching, and layered intermediaries. REST later becomes the dominant conceptual foundation for HTTP APIs and many frontend-backend integrations. LINK *** ## NODE 28 NAME WEB MIDDLEWARE PIPELINE DATE 2000 PLACE GLOBAL WHO WEB SERVER AND FRAMEWORK COMMUNITY BRIEF DESCRIPTION Web frameworks increasingly organize request processing as a sequence of reusable middleware components. Authentication, sessions, compression, logging, validation, routing, caching, and error handling can operate around application-specific controllers without being duplicated inside every endpoint. LINK *** ## NODE 29 NAME ECLIPSE PLUGIN ARCHITECTURE DATE 2001-11 PLACE GLOBAL WHO IBM AND ECLIPSE COMMUNITY BRIEF DESCRIPTION Eclipse is released as an extensible platform whose functionality is assembled from plugins. Plugins declare dependencies and extension points through metadata and can add new behavior without changing the platform core. Plugin architecture becomes a major example of deployment-time application extensibility. LINK *** ## NODE 30 NAME ENTERPRISE APPLICATION ARCHITECTURE PATTERNS DATE 2002 PLACE GLOBAL WHO Martin Fowler and enterprise software community BRIEF DESCRIPTION Patterns of Enterprise Application Architecture consolidates a vocabulary for recurring application components and relationships. Patterns including Service Layer, Repository, Data Mapper, Gateway, Front Controller, Application Controller, Domain Model, Unit of Work, and others become widely used architectural concepts. LINK *** ## NODE 31 NAME SERVICE LAYER DATE 2002 PLACE GLOBAL WHO Martin Fowler and enterprise application community BRIEF DESCRIPTION The Service Layer pattern defines an application boundary that coordinates use cases and exposes operations while separating them from presentation and persistence concerns. The modern application service component emerges as a distinct architectural role responsible for orchestration and domain workflows. LINK *** ## NODE 32 NAME REPOSITORY PATTERN DATE 2002 PLACE GLOBAL WHO Eric Evans, Martin Fowler and enterprise software community BRIEF DESCRIPTION The Repository pattern establishes an abstraction between domain or service logic and mechanisms used to retrieve and persist entities. Application logic can depend on repository contracts instead of directly embedding SQL, database drivers, remote calls, or persistence-specific operations. LINK *** ## NODE 33 NAME APPLICATION CONTROLLER DATE 2002 PLACE GLOBAL WHO ENTERPRISE APPLICATION COMMUNITY BRIEF DESCRIPTION The Application Controller pattern separates navigation and application-flow decisions from individual user-interface screens and domain objects. Controllers increasingly become explicit components responsible for converting external interaction into application use cases. LINK *** ## NODE 34 NAME RUBY ON RAILS DATE 2004 PLACE GLOBAL WHO David Heinemeier Hansson BRIEF DESCRIPTION Ruby on Rails popularizes convention-over-configuration Web application development based on Model-View-Controller, Active Record persistence, routing, controllers, templates, migrations, and reusable plugins. Full-stack Web architecture becomes highly standardized and rapidly reproducible. LINK *** ## NODE 35 NAME AJAX WEB APPLICATIONS DATE 2005 PLACE GLOBAL WHO Jesse James Garrett and Web development community BRIEF DESCRIPTION The term Ajax consolidates techniques for Web applications that communicate asynchronously with servers without replacing the entire page. The browser frontend becomes increasingly stateful and interactive while backend systems expose data-oriented endpoints instead of only generating complete HTML documents. LINK *** ## NODE 36 NAME RICH WEB FRONTEND DATE 2005 PLACE GLOBAL WHO WEB DEVELOPMENT COMMUNITY BRIEF DESCRIPTION Asynchronous HTTP requests, DOM manipulation, JavaScript, CSS, and browser APIs transform the frontend into an independently complex application subsystem. A stronger architectural separation develops between frontend presentation and interaction logic and backend domain, security, and persistence services. LINK *** ## NODE 37 NAME JQUERY DATE 2006-08-26 PLACE USA WHO John Resig BRIEF DESCRIPTION jQuery provides a common abstraction over inconsistent browser APIs and makes DOM manipulation, events, animations, and asynchronous requests easier to implement. Reusable frontend libraries accelerate the transition from server-generated pages toward increasingly sophisticated browser applications. LINK *** ## NODE 38 NAME RABBITMQ DATE 2007-02 PLACE GLOBAL WHO LShift, CohesiveFT and RabbitMQ community BRIEF DESCRIPTION RabbitMQ publicly releases an open-source message broker implementing AMQP. Application components can communicate asynchronously through exchanges and queues instead of requiring direct synchronous calls. Messaging enables decoupled workers, background jobs, event processing, retries, and independent scaling. LINK *** ## NODE 39 NAME BACKGROUND WORKER ARCHITECTURE DATE 2007 PLACE GLOBAL WHO DISTRIBUTED APPLICATION COMMUNITY BRIEF DESCRIPTION Message brokers and application job queues make the worker a common backend architectural component. User-facing requests can enqueue expensive or slow operations while independent worker processes execute them asynchronously, improving responsiveness, fault isolation, and horizontal scalability. LINK *** ## NODE 40 NAME NODE.JS DATE 2009 PLACE USA WHO Ryan Dahl and open source community BRIEF DESCRIPTION Node.js brings JavaScript to server-side application development using an event-driven, non-blocking I/O architecture. The same language can now operate on both frontend and backend while asynchronous event loops provide an efficient model for APIs, gateways, real-time systems, and network services. LINK *** ## NODE 41 NAME CELERY DISTRIBUTED TASK QUEUE DATE 2009 PLACE GLOBAL WHO Ask Solem and Python community BRIEF DESCRIPTION Celery develops as a distributed task queue for Python applications. Applications can submit background jobs to brokers while independent workers execute tasks according to routing, retry, scheduling, and concurrency policies. Worker and scheduler roles become explicit reusable application infrastructure. LINK *** ## NODE 42 NAME ANGULARJS DATE 2010 PLACE USA - California WHO Miško Hevery, Adam Abrons and GOOGLE BRIEF DESCRIPTION AngularJS provides a browser-side application framework based on templates, controllers, dependency injection, routing, binding, and reusable components. Complex frontend applications increasingly acquire internal architecture comparable in sophistication to traditional backend applications. LINK *** ## NODE 43 NAME TWELVE-FACTOR APPLICATION DATE 2011 PLACE USA - California WHO Adam Wiggins and HEROKU BRIEF DESCRIPTION The Twelve-Factor methodology describes application practices suited to cloud deployment, including explicit dependencies, external configuration, stateless processes, disposable instances, environment parity, backing services, and logs as event streams. Application architecture becomes more explicitly separated from infrastructure configuration. LINK *** ## NODE 44 NAME SINGLE-PAGE APPLICATION ARCHITECTURE DATE 2012 PLACE GLOBAL WHO WEB APPLICATION COMMUNITY BRIEF DESCRIPTION Modern browser frameworks consolidate the Single-Page Application pattern. Routing, interface state, rendering, validation, and substantial application logic execute on the client while servers increasingly expose reusable APIs. Frontend and backend become independently developed architectural subsystems. LINK *** ## NODE 45 NAME REACT DATE 2013-05-29 PLACE USA - California WHO Jordan Walke and FACEBOOK BRIEF DESCRIPTION React is open-sourced as a library for constructing user interfaces from reusable declarative components. UI state and rendering are decomposed into composable component trees. Component-oriented frontend architecture becomes one of the dominant models for modern Web applications. LINK *** ## NODE 46 NAME NETFLIX ZUUL DATE 2013 PLACE USA - California WHO NETFLIX BRIEF DESCRIPTION Netflix develops Zuul as an edge service that routes requests into a large distributed service architecture. Cross-cutting concerns such as routing, authentication, monitoring, resiliency, traffic shaping, and dynamic filtering can be concentrated at a gateway rather than independently implemented by every service. LINK *** ## NODE 47 NAME API GATEWAY DATE 2013 PLACE GLOBAL WHO CLOUD AND MICROSERVICES COMMUNITY BRIEF DESCRIPTION The API Gateway emerges as a distinct architectural component positioned between external clients and collections of backend services. It can provide routing, authentication, authorization, rate limiting, protocol translation, response aggregation, observability, and other perimeter policies. LINK *** ## NODE 48 NAME MICROSERVICES ARCHITECTURE DATE 2014-03-25 PLACE GLOBAL WHO James Lewis, Martin Fowler and distributed software community BRIEF DESCRIPTION Microservices are clearly articulated as an architectural style in which an application is composed of small independently deployable services organized around business capabilities. Application boundaries move from internal modules toward independently operated network services with their own deployment and often their own persistence. LINK *** ## NODE 49 NAME SERVERLESS APPLICATION ARCHITECTURE DATE 2014-11-13 PLACE USA WHO AMAZON WEB SERVICES BRIEF DESCRIPTION AWS Lambda introduces an execution model in which application code runs in response to events while the cloud provider manages servers, scaling, and runtime capacity. Functions become independently deployable backend components connected to APIs, queues, storage systems, databases, and event streams. LINK *** ## NODE 50 NAME GRAPHQL DATE 2015 PLACE USA - California WHO FACEBOOK BRIEF DESCRIPTION Facebook open-sources GraphQL as a strongly typed query language and runtime for APIs after using it internally since 2012. Frontend applications can request precisely structured data through schemas rather than requiring a separate fixed REST representation for every interface need. LINK *** ## NODE 51 NAME GRPC DATE 2015-03 PLACE USA - California WHO GOOGLE AND OPEN SOURCE COMMUNITY BRIEF DESCRIPTION Google open-sources gRPC as a high-performance remote procedure call framework based on Protocol Buffers and HTTP/2. Explicit service definitions generate client and server bindings across programming languages, making typed RPC a major communication model for internal backend services. LINK *** ## NODE 52 NAME BACKEND FOR FRONTEND DATE 2015-11-18 PLACE GLOBAL WHO Phil Calçado, Sam Newman, SoundCloud and microservices community BRIEF DESCRIPTION The Backend for Frontend pattern formalizes the use of a dedicated backend component for a particular user experience. Web, mobile, desktop, or external clients can each receive an API optimized for their requirements instead of depending on one generalized gateway or backend. LINK *** ## NODE 53 NAME CONTAINER-ORCHESTRATED APPLICATION DATE 2015 PLACE GLOBAL WHO KUBERNETES AND CLOUD NATIVE COMMUNITY BRIEF DESCRIPTION As Kubernetes reaches production maturity, independently deployable application components increasingly run as containerized workloads managed through declarative deployment, services, health checks, configuration, scaling, and controllers. Deployment topology becomes distinct from the logical application source tree. LINK *** ## NODE 54 NAME CIRCUIT BREAKER APPLICATION PATTERN DATE 2014 PLACE GLOBAL WHO Michael Nygard, Martin Fowler and distributed systems community BRIEF DESCRIPTION The Circuit Breaker pattern becomes widely adopted for remote application dependencies. Instead of repeatedly invoking an unhealthy service until resources are exhausted, applications detect failures, temporarily stop calls, and allow controlled recovery. Failure-handling policy becomes an explicit architectural component. LINK *** ## NODE 55 NAME SERVICE MESH DATE 2017-05-24 PLACE GLOBAL WHO GOOGLE, IBM, LYFT AND ISTIO COMMUNITY BRIEF DESCRIPTION Istio introduces a service-mesh architecture that moves service-to-service networking concerns into infrastructure proxies and control-plane components. Traffic routing, mutual authentication, telemetry, retries, policy, and service communication can be managed separately from business application code. LINK *** ## NODE 56 NAME EDGE APPLICATION RUNTIME DATE 2017 PLACE GLOBAL WHO CLOUDFLARE AND EDGE COMPUTING COMMUNITY BRIEF DESCRIPTION Edge function platforms begin allowing application logic to execute geographically close to users rather than only in centralized application servers or cloud regions. Routing, personalization, security, lightweight computation, and request transformation can occur at the application perimeter. LINK *** ## NODE 57 NAME UI COMPOSITION AND MICRO-FRONTENDS DATE 2019 PLACE GLOBAL WHO WEB ARCHITECTURE COMMUNITY BRIEF DESCRIPTION Micro-frontend and UI composition patterns apply independently deployable component principles to frontend systems. Different teams can own sections of a larger user experience while runtime or build-time composition presents them as one application. LINK *** ## NODE 58 NAME OBSERVABILITY-AWARE APPLICATION ARCHITECTURE DATE 2019 PLACE GLOBAL WHO OPENTELEMETRY AND CLOUD NATIVE COMMUNITY BRIEF DESCRIPTION Distributed traces, metrics, logs, health checks, and correlation identifiers increasingly become standard application interfaces rather than optional debugging additions. Modern controllers, services, workers, gateways, and background processes are designed with explicit observability behavior. LINK *** ## NODE 59 NAME EVENT-DRIVEN CLOUD APPLICATIONS DATE 2020 PLACE GLOBAL WHO CLOUD NATIVE COMMUNITY BRIEF DESCRIPTION Cloud applications increasingly combine synchronous APIs with asynchronous events, message brokers, queues, functions, streams, schedulers, and workers. Application flow becomes a graph of independently triggered components rather than a single request-response call chain. LINK *** ## NODE 60 NAME REACT SERVER COMPONENT ARCHITECTURE DATE 2020-12 PLACE USA - California WHO REACT TEAM BRIEF DESCRIPTION React Server Components introduce a model in which portions of a component-oriented user interface can execute on the server while other components remain interactive on the client. The traditional frontend-backend boundary becomes more flexible while preserving component composition. LINK *** ## NODE 61 NAME DISTRIBUTED APPLICATION CONTROL PLANE DATE 2021 PLACE GLOBAL WHO CLOUD NATIVE SOFTWARE COMMUNITY BRIEF DESCRIPTION Application architecture increasingly distinguishes data-plane components that execute user workload from control-plane components that configure, reconcile, route, secure, deploy, and observe those workloads. Controllers themselves become fundamental components of large distributed applications. LINK *** ## NODE 62 NAME EDGE SERVERLESS APPLICATIONS DATE 2022 PLACE GLOBAL WHO CLOUD AND EDGE COMPUTING COMMUNITY BRIEF DESCRIPTION Serverless functions, key-value stores, databases, queues, and application middleware increasingly become available at globally distributed edge locations. Applications can combine browser components, edge handlers, regional services, workers, and centralized persistence in one logical system. LINK *** ## NODE 63 NAME COMPOSABLE FULL-STACK APPLICATION DATE 2023 PLACE GLOBAL WHO WEB AND CLOUD DEVELOPMENT COMMUNITY BRIEF DESCRIPTION Modern full-stack frameworks increasingly combine server rendering, client components, API endpoints, middleware, background jobs, caching, edge execution, database integration, authentication, and deployment metadata within one development environment while preserving separate runtime components. LINK *** ## NODE 64 NAME AI-ASSISTED APPLICATION COMPONENT DATE 2024 PLACE GLOBAL WHO APPLICATION AND ARTIFICIAL INTELLIGENCE COMMUNITY BRIEF DESCRIPTION Applications increasingly incorporate model inference as a separate service or component alongside conventional controllers, services, repositories, workers, and APIs. Model gateways, retrieval systems, asynchronous inference workers, safety checks, and streaming interfaces introduce new backend architectural roles without replacing established application architecture. LINK *** ## NODE 65 NAME HYBRID MODULAR APPLICATION ARCHITECTURE DATE 2025 PLACE GLOBAL WHO SOFTWARE ARCHITECTURE COMMUNITY BRIEF DESCRIPTION Application teams increasingly select architecture according to operational requirements rather than treating maximum distribution as an objective. Well-structured modular monoliths, independently deployable services, asynchronous workers, serverless functions, edge components, and managed services can coexist within the same system. LINK *** ## NODE 66 NAME MODERN APPLICATION ARCHITECTURE DATE 2026 PLACE GLOBAL WHO GLOBAL SOFTWARE ENGINEERING COMMUNITY BRIEF DESCRIPTION A modern application can contain frontend components, backend controllers, domain services, repositories, APIs, gateways, middleware, workers, schedulers, plugins, queues, databases, functions, edge runtimes, AI services, and control-plane infrastructure. These components may execute within one process or across thousands of distributed processes. The central architectural problem is no longer merely dividing code, but defining explicit responsibilities, contracts, data flows, failure boundaries, deployment boundaries, and observable relationships among independently evolving components. LINK