PLoP = Pattern Languages of Programs, a group that collects good patterns like some people collect baseball cards.
Some interesting links:
Books On Patterns
Patterns Catalog
Some Random Interesting Patterns:
Avionics Patterns
Scrum Patterns
Other Links:
Pattern-Oriented Software Architectures
Patterns & Frameworks for
Concurrent & Distributed Systems - Patterns For Real Time Avionics Messaging in UAV
Great Article on Inversion of Control Layer
Variability Patterns (Software Product Line)
Showing posts with label patterns. Show all posts
Showing posts with label patterns. Show all posts
Saturday, August 20, 2011
Monday, March 28, 2011
Common JEE Application Design Patterns
- Typesafe enum pattern/enum in JDK 1.5+
- code to an interface not an implementation
- abstract parent class to promote reuse for subclasses
- factory method pattern (loose couples calling code from instances created)
- abstract factory pattern (specific method for each concrete type)
- builder pattern (similar to factory except user had more flexibility (builder.add(x), builder.add(y), etc.)
- strategy pattern (strategy encapsulates algorithms not data)
- decorator design pattern: (implements same interface as object it decorates)
- visitor pattern: (avoids lots of typecasts and instanceof to do common method on different types)
- iterator pattern
- template method pattern (e.g. Spring JDBC and Spring JMS)
- composite design pattern: (act on Manager or Staff object in same way. both subs of employee)
- facade pattern: (interface to large set of classes)
- observer pattern: (observer registers with publisher, publisher notifies observer of event)
- command pattern: OO equivalent of callbacks (sender object invokes operation, receiver object receives request to execute certain operation)
- proxy pattern: (remote: EJB, RMI, CORBA, virtual: create memory intensive object on demand (lazy load hibernate objects when needed), access: different clients get different access rights)
- dynamic proxy: (reflection based; come at a performance cost; common in AOP)
- adapter pattern (wrap API)
- service activator pattern (ala MessageBean) services need a way to be activated asynchronously
- For completion: (bridge, chain of responsibility)
- For completion JEE (MVC, front controller, composite view, view helper, dispatcher view, service to worker, business delegate, session facade, value object, fast lane reader, service locator)
Sunday, February 14, 2010
GoF Design Patterns
From the now-classic book Design Patterns: Elements of Reusable Object-Oriented Software
.
Creational Patterns
Creational Patterns
- Abstract Factory: Creates an instance of several families of classes
- Builder: Separates object construction from its representation
- Factory Method: Creates an instance of several derived classes
- Prototype: A fully initialized instance to be copied or cloned
- Singleton: A class of which only a single instance can exist
- Adapter: Match interfaces of different classes
- Bridge: Separates an object’s interface from its implementation
- Composite: A tree structure of simple and composite objects
- Decorator: Add responsibilities to objects dynamically
- Facade A single class that represents an entire subsystem
- Flyweight: A fine-grained instance used for efficient sharing
- Proxy: An object representing another object
- Chain of Resp.: A way of passing a request between a chain of objects
- Command: Encapsulate a command request as an object
- Interpreter: A way to include language elements in a program
- Iterator: Sequentially access the elements of a collection
- Mediator: Defines simplified communication between classes
- Memento: Capture and restore an object's internal state
- Observer: A way of notifying change to a number of classes
- State: Alter an object's behavior when its state changes
- Strategy: Encapsulates an algorithm inside a class
- Template Method: Defer the exact steps of an algorithm to a subclass
- Visitor: Defines a new operation to a class without change
Software Architecture Patterns
Patterns from Pattern-Oriented Software Architecture Volume 1: A System of Patterns

Architectural Patterns
Design Patterns
Architectural Patterns
- Layers
- Pipes and Filters
- Blackboard
- Distributed Systems
- Broker
- Interactive Systems
- Model-View-Controller
- Presentation-Abstraction-control
- Adaptable Systems
- Microkernel
- Reflection
Design Patterns
- Whole-Part
- Organization of Work
- Master-Slave
- Access Control
- Proxy
- Management
- Command Processor
- View Handler
- Communication
- Forwarder-Receiver
- Client-Dispatcher-Server
- Publisher-Subscriber
Enterprise Design Patterns
- Acid Transaction
- Composite Transaction
- Two Phase Commit
- Audit Trail
- Shared Object
- Object Request Broker
- Object Replication
- Redundant Independent Objects
- Prompt Repair
- Mobile Agent
- Demilitarized Zone
- Process Pairs
- Object Identifier
- Registry
- Protection Proxy
- Publish-Subscribe
- Retransmission
- MailboxHeavyweight/Lightweight
- Heartbeat
- Connection Multiplexing
- Session Object
- Lock File
- Static Locking Order
- Optimistic Concurrency
- Thread Pool
- Ephemeral Cache Item
- Transaction State Stack
- Time Server
- Versioned Object
- Temporal Property
- Persistence Layer
- CRUD
- Stale Object
- Type Conversion
- IsDirty
- Lazy Retrieval
Labels:
architecture,
concurrency,
database,
patterns
Subscribe to:
Posts (Atom)