FAST - Free All Scrumbled Thoughs. Publish–subscribe pattern. In software architecture, publish–subscribe is a messaging pattern where senders of messages, called publishers, do not program the messages to be sent directly to specific receivers, called subscribers. Instead, published messages are characterized into classes, without knowledge of what, if any, subscribers there may be. Similarly, subscribers express interest in one or more classes, and only receive messages that are of interest, without knowledge of what, if any, publishers there are. Pub/sub is a sibling of the message queue paradigm, and is typically one part of a larger message-oriented middleware system. Most messaging systems support both the pub/sub and message queue models in their API, e.g. Java Message Service (JMS). This pattern provides greater network scalability and a more dynamic network topology.
Message filtering[edit] In the pub/sub model, subscribers typically receive only a subset of the total messages published. Topologies[edit] History[edit] Advantages[edit] Facade pattern. The facade pattern (or façade pattern) is a software design pattern commonly used with object-oriented programming. The name is by analogy to an architectural facade. A facade is an object that provides a simplified interface to a larger body of code, such as a class library. A facade can: Usage[edit] Structure[edit] Facade The facade class abstracts Packages 1, 2, and 3 from the rest of the application. Clients The objects are using the Facade Pattern to access resources from the Packages. Example[edit] This is an abstract example of how a client ("you") interacts with a facade (the "computer") to a complex system (internal computer parts, like CPU and HardDrive).
References[edit] Jump up ^ Freeman, Eric; Freeman, Elisabeth; Kathy, Sierra; Bert, Bates (2004). External links[edit] Description from the Portland Pattern Repository. Scalable JavaScript Application Architecture - Microsoft UK Developers. View all articles My Summary: Nicholas showed a technique to build large scale applications, one which he used during his time as an engineer at Yahoo. The technique had specific relevance to single page applications all though could be employed on Multiple page applications as well. The architecture he described split an application into multiple tiers with each tier having specific roles and responsibilities and loosely coupled so that elements could be removed, replaced or updated. Slides from the talk are over on slide share. Nicholas Zakas is a regular speaker on the JavaScript circuit but for some reason I'd always missed his talks at other conferences.
The Abstract: Building large web applications with dozens of developers is a difficult task. Nicholas took the stage and asked "How many people are building single page JavaScript applications? " Many people are using Application frameworks like backbone.js, but many don't realise it's actually pretty easy to build your own. Nicholas Zakas: Scalable JavaScript Application Architecture. ScaleApp. Flosse/scaleApp. ScaleApp: no deps, tiny, PageApps, plugins.