From 7c88086cc4f403f5b5c552d1130e045616c07d5f Mon Sep 17 00:00:00 2001 From: Andy Ko Date: Thu, 15 Jun 2017 10:57:01 -0700 Subject: [PATCH] Added event-driven architectures. --- architecture.html | 1 + 1 file changed, 1 insertion(+) diff --git a/architecture.html b/architecture.html index 63390f4..f956f0c 100644 --- a/architecture.html +++ b/architecture.html @@ -40,6 +40,7 @@
  • Pipe and filter, in which data is passed from component to component, and transformed and filtered along the way. Command lines, compilers, and machine learned programs are examples of pipe and filter architectures.
  • Model-view-controller (MVC), in which data is separated from views of the data and from manipulations of data. Nearly all user interface toolkits use MVC, including popular modern frameworks such as React.
  • Peer to peer (P2P), in which components transact data through a distributed standard interface. Examples include Bitcoin, Spotify, and Gnutella. +
  • Event-driven, in which some components "broadcast" events and others "subscribe" to notifications of these events. Examples include most model-view-controller-based user interface frameworks, which have models broadest change events to views, so they may update themselves to render new model state.

    Architectural styles come in all shapes and sizes. Some are smaller design patterns of information sharing (Beck et al. 2006), whereas others are ubiquitous but specialized patterns such as the architectures required to support undo and cancel in user interfaces (Bass et al. 2004).