Skip to main content

Good Read: MSDN Dependency Injection

Dependency Injection (DI) design pattern is a common used design patterns in real-time applications as it allows us to develop loosely coupled software components.
 

Photo by Scott Webb from Pexels - modified by Beolle


You have probably heard about the Factory Pattern and the separation between the interface and the implementation using services, where the client objects are often responsible for service location.
The Dependency Injection pattern is a particular implementation of Inversion of Control. Inversion of Control (IoC) means that objects do not create other objects on which they rely to do their work. Instead, they get the objects that they need from an outside source (for example, an xml configuration file).
Dependency Injection (DI) means that this is done without the object intervention, usually by a framework component that passes constructor parameters and set properties."

Paragraph from articleASP.NET MVC 4 Dependency Injection

Fantastic read about these patterns at MSDN location.

Recommend both links.

Trending posts

Headless CMS - yet another CMS comparison

If you have used, or are familiar with the term headless CMS (content management system), then you will know the reason behind it. In summary a CMS is called headless because there is no Front end (FE), or output coupled with the CMS. Instead the CMS supports APIs which expose the content that can be consumed by external applications.                                                                 Photo by fotografierende from Pexels We could say that a decoupling from the CMS is provided, allowing, for those that have chosen this alternative, a certain sense of “freedom” in selecting the FE of the solution. There are many reasons for selecting the most popular, and so called “traditional” CMSs in the market. Even though, not sure if it is proper to call them “traditional” anymore as they keep evolving, becoming stronger and versatile and offering new services including SaaS. Even some are providing a flavor of headless. I have my fair share of experience using some of the greatest

Essence of email deliverability - SPF, DKIM, DMARC and segmentation

Recently I attended a lively discussion on email deliverability hosted by Litmus, one of the leading providers of email marketing tools. As email marketers one of the core metrics we often rely on is email deliverability and the discussion was around how to improve the email deliverability in today’s world where our audiences are ever inundated with emails. In addition we often find ourselves operating in a very competitive landscape vying for these audiences' precious attention. Photo by Ivan Samkov from Pexels   Hence it’s becoming increasingly important to ensure our emails are reaching our audiences’ inbox and driving engagement. This is why email clicks and engagement are strong indicators of the performance of our email campaigns instead of just the delivery rate of our campaigns partly thanks to Apple’s Mail Privacy Protection . So let’s start with the distinction between email delivery and email deliverability . This is very well articulated by Dimiter Batmaziam in the Li

Blue Ocean Strategy in the new reality

Photo by Kammeran Gonzalez-Keola from Pexels Since the COVID lockdown started over a year ago I have seen many restaurants in my neighborhood go through transformations - many became available in the top three delivery service: Ubereats, Doordash and Skipthedishes while the rest transformed to support pick up service and patio dining. However, among all of them, one of my favorite Indian restaurants impressed me the most.  The restaurant initially became available via the delivery services just after the lockdown in early 2020. I first ordered from the restaurant via Ubereats. In the delivery the restaurant included a pamphlet encouraging me to order from them directly on their website with an initial enticing offer. I ordered immediately after a few days from their website. I was guided to create an account and subscribe to their newsletter in the process.  The delivery for the order was on time and the food as always was delicious and of high quality. In a few days I received a

Goal setting frameworks for Product Management - OKR and HOSKR

As a business analyst and product manager we often use various frameworks to synthesize and organize our product ideas and goals. I think of frameworks as tools in our product management tool kit which we use depending on the task at hand.  And speaking of goals, OKR is a very popular framework that I often use to set the goals for the products I am managing. However recently I participated the #ProductCon conference hosted by Product School  and I stumbled upon one of the talks in which Rapha Cohen, the CPO at Google Waze introduced a more effective framework for setting product goals. The framework is called HOSKR.  In this post I'll describe both the OKR and HOSKR frameworks in more details using examples. I hope this will provide you, our readers, more practical insights on how to effectively use these frameworks to set your product goals.  OKR OKR stands for O bjectives and K ey R esults. If you are reading this post then you are on our Beolle blog and I am going to use one o

This blog uses cookies to improve your browsing experience. Simple analytics might be in place for pageviews purposes. They are harmless and never personally identify you.

Agreed