Adapter pattern is a design pattern that allows objects with incompatible interfaces to work together by converting the interface of one object into an interface expected by the client. This pattern involves creating a wrapper class that implements the target interface and delegates calls to the adaptee object. The adapter acts as a bridge between the adaptee and client, allowing them to work together even if their interfaces are not compatible.

Business Delegate pattern provides a simplified interface to a set of services to reduce the coupling between presentation-tier clients and business services.

The Builder Pattern is used when the construction of an object is complex, and it allows you to build objects step by step, with each step having a different number of options. This is useful when you want to provide a clean API for creating objects, without exposing the details of the creation process. The Factory Pattern, on the other hand, is used when you need to create objects with a single method call. This is useful when the creation process is simple, and you don't need to provide a clean API for creating objects.

The Service Locator pattern involves a centralized object that provides access to dependencies, while Dependency Injection provides objects to dependencies through constructor injection, method injection, or setter injection.

The Intercepting Filter pattern is a design pattern used in web applications to pre-process requests before they are sent to the target resource. This is done to add additional functionality to the request such as security checks, data validation, or header modification.

The Factory pattern is a creational design pattern that provides a way to create objects in a more efficient and centralized manner. The Factory pattern abstracts the process of object creation and allows the client code to be decoupled from the actual implementation of the objects being created. This allows for greater flexibility and maintainability in the code, as the specific implementation of the objects can be changed without affecting the client code.

Facade pattern is a design pattern that provides a simplified interface to a complex system, allowing the client to interact with the system through a single, unified interface. The pattern involves creating a facade class that acts as a wrapper around the complex system, providing a simplified interface to the client. This pattern can be useful in situations where you want to simplify the interface of a complex system, making it easier for clients to use the system.

The Command pattern is used to allow sending requests to objects without knowing anything about the operation being requested or the receiver of the request. It provides a way to queue or log requests and acts as a marshal between the sender and the receiver.

The choice between Repository Pattern and "smart" business objects depends on the specific requirements of the project, but in general the Repository Pattern provides better separation of concerns and a common interface for data access.

The State pattern is a design pattern in which an object, called the context, holds a reference to an instance of one of several possible concrete state objects, each of which represents a distinct state of the context and implements a common state interface. The State pattern allows the context's behavior to be altered dynamically by changing its state. The State pattern is used to implement state machines, allowing an object's behavior to be altered as its internal state changes.