Design patterns (short description)

2020-04-11T04:19:00.000-07:00

Here is some short description of GoF design patterns. It is just to remind the explanations. so first you have to understand each design pattern separately.

Adapter Pattern:

Convert the interface of a class into some other classes that client expects. Adapter lets classes work together that couldn't otherwise because of incompatible interfaces.

Decorator Pattern: (alternate of sub classing)

Attach additional responsibilities to an object at run-time. It follow closed for modification but open for extension SOLID rule.

Strategy Pattern: (Reduce IFs)

Define a family of algorithms, encapsulate each one, and make them interchangeable. Strategy lets the algorithm vary independently from client that use it.

Template method pattern:

Define the skeleton of an algorithm in an operation, differing same steps to sub classes. Template method lets sub classes redefine certain steps of an algorithm without changing the algorithm structure.

Visitor Pattern

Represent an operation to be performed on the elements of an object structure. Visitor lets you define a new operation without changing the classes of the elements on which it operates.

Ex :calculate IsAboveEighteen by introducing same new property in same class.

Observer Pattern:

Define a one to one dependency between objects so that when one object changes state, all its dependents are notified and updated automatically.

Builder pattern:

Separate the construction of complex object from its representation so that the same construction process can create different representation. Ex: different configuration computer assembling by robots

Chain of responsibility:

Avoid coupling of the sender of a request to its receiver by giving more than one object a chance to handle the request.

Ex: Logic logic =new Logic();

logic.Receiver=new Logger(new Email(null));

logic.HandleMessage();

Abstract Factory pattern:

Provides an interface for creating families of related dependent object without specifying their concrete classes. Ex: DbProviderFactory

Factory Pattern:

Define an interface for creating an object but let classes decide which class to instantiate. Factory method lets a class defer instantiation to sub classes.

Generic Modifier In & Out C#

2018-10-15T09:25:00.002-07:00

In [Contravariant]

The image is self-explanatory.

Out [Covarient]

The image is self-explanatory.

Reduce your Azure Development Subscription Cost

2018-09-11T11:14:00.003-07:00

Azure VMs

Usually you should convey to developers and testers to shut down the VMs manually when they are not using non production virtual machines. Also there some ways to automatic shutdown the VMs like you can create and schedule a script to start and shutdown VMs based on use timings or you can use Dev Test labs.

Azure App Services

As app service plan allocate compute resources for which you pay so if you run multiple applications in same app service plan, that will definitely reduce your cost. If your app service plan tier is not fulfilling your new app requirements like it requires high computation resources or your exiting app service plan is already exceeding the resource utilization, than its better to create new one.

Learning Microsoft Technologies.......

Design patterns (short description)

Adapter Pattern:

Decorator Pattern: (alternate of sub classing)

Strategy Pattern: (Reduce IFs)

Template method pattern:

Visitor Pattern

Observer Pattern:

Builder pattern:

Chain of responsibility:

Abstract Factory pattern:

Factory Pattern:

Generic Modifier In & Out C#

In [Contravariant]

Out [Covarient]

Reduce your Azure Development Subscription Cost

Azure VMs

Azure App Services