Morteza Sahragard

Recently I saw some discussions on Twitter people arguing about necessity of existence of ORMs (Object-relational mapping) at this age and the others are even waiting to have Entity Framework as a binging in Azure Functions. That made me as a person who have been working with ORMs from the early days and with different types of data driven applications, to write my two cents about the topic.

If you have been doing Serverless Programming in Micrpsft Azure Stack, you probably know that the new generation of Functions (v2) has been available now for a few months. There are some differences in the new versions compared to the old one that you need to know before migrating your existing Functions.

First of all, why do we need lazy object initialization? The answer is that when initialization of an object for whatever reason is expensive, we would typically wish to instantiate it once and only when it's required. There is an API introduced in .NET Framework called Lazy<T> for this purpose.

INotifyPropertyChanged is a standard interface available form the early versions of .NET but still so popular. The general idea behind the implementation of this interface is awareness of the changes in the value of the properties in a class.

What I am going to be talking about today is neither new nor complicated. But doing code review, I still see many developers and even experienced ones make this mistake while handling exceptions.

BlockingCollection is a class under System.Collections.Concurrent namespace and as the name implies, like any other collections under this namespace, it can also be used in concurrent and multi-tasking scenarios.

Now a days, it has become highly unlikely to find a robust software design and architecture which is not utilizing interfaces. During development, it's sometimes really frustrating to find the implementations of a method of an interface.

Well, as web developers, we are always dealing with JSON data which are coming from different sources. Either we are serializing our own entities or it's coming from the external sources like third-party services and so on.