Skip to main content

Null object pattern - design pattern

Acest design pattern ar trebui sa ne ajute pentru a elimina sau cel putin sa reducem numarul de verificare de genul:
If( obj != null )
{
//Ceva cod.
}
Pentru a putea folosi acest design pattern este nevoie sa declaram o instanta a unui obiect( sau o clasa) care sa joace rolul obiectului care reprezinta valorea null. Exista doua varinte de implementare, de la caz la caz se poate folosi una din ele.
In prima varianta se foloseste o instanta a clasei care joaca rolul de valoarea NULL. Aceasta este oferita dezvoltatorului prin intermediul unei propietati statice.
public class Car
{
public static readonly Car NullObj;

static Car
{
NullObj = new Car();
//Setare valori, propietati cu valori default.
}
}
Deoarece am declarat field-ul ca fiind read-only, setarea acestuia se va putea face doar in constructor. Codul pe care o sa il folosim acuma o sa fie asemanator cu:
if( car == Car.NullObj )
{
//Executa ceva
}
In cazul in care vrem sa apelam metode sau propietati, putem le apelam fara sa facem verificarea daca obiectul este NULL sau nu. O sa putem scrie fara probleme cod de genul:
car.Color;
car.ChangeColor();
O alta varianta care se foloseste cand lucram cu clase abstracte sau cu interfete este sa ne declaram o clasa care sa reprezinte valoarea NULL. Iar aceasta clasa o sa poata fi folosita cand nu avem o instanta a clasei dorite si care poate sa aiba un comportament mai special, de exemplu sa faca o logare.
public abstract class Car
{
public static readonly Car NullObj;

static Car()
{
NullObj = new NullCar();
//Initializare custom daca este nevoie;
}

public class NullCar : Car
{
//Implementare custom pentru clasele abstracte sau virtuale.
}
}
Toate valoriile care o sa reprezinte instance NULL din clasa Car o sa fie de tip NullCar.
Acest pattern nu se poate sa fie folosit in orice caz, dar sunt cazuri cand se preteaza foarte bine. Un caz pe care l-am identificat este cand avem un API( un serviciu) care se ocupa de notificari. Mecanismul prin care se face notificati poate sa fie configurabil( SMS,MSM, email, etc) si chiar schimbat fara sa oprim aplicatia. Pot sa apara cazuri cand acest mecanism sa nu fie configurat, caz in care ar fi nevoie sa verificam inante de a apela metoda care face notificarea daca valoarea este NULL sau nu. Pentru acest caz am putea sa avem ceva de genul:
public interface INotification
{
void Notify();
}
public class NullNotification : INotification
{
public void Notify
{
//Se poate face un login.
}
}
In acest caz, daca nu avem nici un mecanism de notificare configurat, putem ca in NullNotification sa logam aceasta problema.

Comments

Popular posts from this blog

How to audit an Azure Cosmos DB

In this post, we will talk about how we can audit an Azure Cosmos DB database. Before jumping into the problem let us define the business requirement: As an Administrator I want to be able to audit all changes that were done to specific collection inside my Azure Cosmos DB. The requirement is simple, but can be a little tricky to implement fully. First of all when you are using Azure Cosmos DB or any other storage solution there are 99% odds that you’ll have more than one system that writes data to it. This means that you have or not have control on the systems that are doing any create/update/delete operations. Solution 1: Diagnostic Logs Cosmos DB allows us activate diagnostics logs and stream the output a storage account for achieving to other systems like Event Hub or Log Analytics. This would allow us to have information related to who, when, what, response code and how the access operation to our Cosmos DB was done. Beside this there is a field that specifies what was th...

Cloud Myths: Cloud is Cheaper (Pill 1 of 5 / Cloud Pills)

Cloud Myths: Cloud is Cheaper (Pill 1 of 5 / Cloud Pills) The idea that moving to the cloud reduces the costs is a common misconception. The cloud infrastructure provides flexibility, scalability, and better CAPEX, but it does not guarantee lower costs without proper optimisation and management of the cloud services and infrastructure. Idle and unused resources, overprovisioning, oversize databases, and unnecessary data transfer can increase running costs. The regional pricing mode, multi-cloud complexity, and cost variety add extra complexity to the cost function. Cloud adoption without a cost governance strategy can result in unexpected expenses. Improper usage, combined with a pay-as-you-go model, can result in a nightmare for business stakeholders who cannot track and manage the monthly costs. Cloud-native services such as AI services, managed databases, and analytics platforms are powerful, provide out-of-the-shelve capabilities, and increase business agility and innovation. H...

Cloud Myths: Migrating to the cloud is quick and easy (Pill 2 of 5 / Cloud Pills)

The idea that migration to the cloud is simple, straightforward and rapid is a wrong assumption. It’s a common misconception of business stakeholders that generates delays, budget overruns and technical dept. A migration requires laborious planning, technical expertise and a rigorous process.  Migrations, especially cloud migrations, are not one-size-fits-all journeys. One of the most critical steps is under evaluation, under budget and under consideration. The evaluation phase, where existing infrastructure, applications, database, network and the end-to-end estate are evaluated and mapped to a cloud strategy, is crucial to ensure the success of cloud migration. Additional factors such as security, compliance, and system dependencies increase the complexity of cloud migration.  A misconception regarding lift-and-shits is that they are fast and cheap. Moving applications to the cloud without changes does not provide the capability to optimise costs and performance, leading to ...