Chain of creation

Fri, 09 Apr 2010 23:32:17 -0400

Hi guys, I am proposing a new design pattern called chain of creation. Can you please have a look at it and share your thoughts. The new design pattern has several advantages over Factory pattern and is more flexible.

Messaging Design Pattern

Wed, 24 Feb 2010 21:00:11 -0500

The messaging design pattern allows the interchange of information (i.e. messages) between components and applications. A messaging paradigm is widely used in the real world. Messages are interchanged all around us. Entities are constantly sending, receiving and processing messages.

How Yehuda Katz builds modular Ruby code

Mon, 15 Feb 2010 13:47:04 -0500

Katz reviews some work that seeks to decorate a Person class to include teacher traits. A factory that creates a Person proxy decorated with Teacher properties is considered as an approach. But it is criticized.

Few important facts about CBE & True Components

Wed, 09 Sep 2009 23:01:06 -0400

Today software engineering needs better components that can offer benefits comparable to the benefits offered by the components for physical products such as cars or computers. Unfortunately such software components are not yet discovered. Furthermore most experts and researchers erroneously argue such components cant exist, so impossible to discover them

singleton ant-pattern?

Mon, 18 May 2009 21:41:20 -0400

How best would you summarize the disadvantages of a singleton that is non-Read only in a clustered env, given many JVM's thus multiple singletons?

Resource Command Pattern

Sun, 15 Feb 2009 07:21:25 -0500

The main advantage of using this pattern version is flexibility in managing resources and their configuration.

The architectural principle of fully self contained messages

Sun, 23 Nov 2008 07:10:26 -0500

A fully self contained message is a pure and complete representation of a specific event and can be published and archived as such. The message can - instantly and in future - be interpreted as the respective event without the need to rely on additional data stores.

CBSE/COP pattern identical to design of physical products

Thu, 06 Nov 2008 06:35:48 -0500

It is often desirable to design and build many large software applications (especially complex Rich Internet Application for example for emerging cloud computing) similar to component-based engineering employed to design and develop physical products such as cars or computers. Adopting such mature proven processes would increase productivity and quality.

Ripping off services layers, bad idea - about the ESB

Sun, 26 Oct 2008 04:48:00 -0400

Why do we need XI, Sonic, Cordys and Biztalk while we already got our WebSphere ESB... Why having more than one ESB?

JustInTime Configuration

Fri, 03 Oct 2008 02:17:20 -0400

A set of objects of a particular type have shared configuration, this shared configuration keeps changing at runtime. The objects must have latest configuration when certain operations are invoked.

A shared dynamic configuration needs to be made available to the objects just-in-time so that the configuration is latest and valid for the operation invoked.

Configuration Inheritance(CI) Pattern

Tue, 16 Sep 2008 05:19:15 -0400

The Configuration Inheritance Pattern，Its exact name is configuration information inheritance with the template technology. Like class inheritance, the application get functions configuration information from the parent node first, then extend and override the configuration information.

Intelligent Lazy [IL] Pattern

Fri, 29 Aug 2008 08:16:43 -0400

IL Pattern is a kind of lazy object creation pattern. Object Creator waits until all or required informations to start creating the object. This will make sure that the object created is perfect so that the next part of a program can use it with out any issues.

Message Access Object (MAO)

Sun, 01 Jun 2008 03:10:24 -0400

1. Hiding message access from client side code
2. Handling JMS related exception handling.

Building an application by assembling Replaceable Components

Sun, 25 May 2008 00:23:32 -0400

This pattern shows a process for building Replaceable Components and assembling them to build larger and larger Replaceable Components and finally an application (e.g. RIA). Each Replaceable component is designed for easy disassembling for example to redesign its code free from rest of the code base of the application and test it before reassembling it.

Session management shift pattern in RIA

Sun, 27 Apr 2008 12:05:50 -0400

In Short: User Session belongs to a browser instances, keep it where it belongs

Problem: The problems in having server side session are provided below:
1.Hit on server scalability; even if we keep only minimum data in session (based on users)
2.The performance impact of round-trips of passing the session data to browser
3. Cookie has size restrictions

Support Forums : Thread List - J2EE patterns