Want to read the greatest and the latest updates on .NET? You’ve come to the right place!
Posts
-
Full Stack C# Development With Blazor
C#, one of the most popular programming languages, is primarily used for back-end development. But in today’s world, industry standards have changed, meaning that full-stack developers are more sought after than their front or back-only counterparts.
-
SOLID Series: The Open Closed Principle
In this article we are going to discuss the Open-Closed As noted by the author of the principles himself, the Open-Closed principle is the most important of concepts in object-oriented programming.
-
Clean Architecture Series: Frameworks
Frameworks are good things - they can relieve you of great pains when developing software. However, committing to a certain framework is like marrying that framework (i.e. you’re bound to using it for the rest of the life cycles of that application). Like Uncle Bob put it: “For better or for worse, in sickness and in health, for richer, for poorer, forsaking all others, you will be using that framework!”.
-
Clean Architecture Series: The Web
For many of today’s systems, the Web is the way to go. Want to build a new application? You would want it to be delivered over the Web, of course, because this is what everybody else is doing, right? Wrong. GUIs are a manner of sending (and sometimes getting) the information to (and from) the user. It has nothing to do whatsoever with the business core of the application and therefore should be regarded as a detail.
-
Clean Architecture Series: The Database
Because it holds the physical representation of a Model (which in turn is critical to the existence of a software system), the Data is certainly very important. When Edgar Codd defined the principles of Relational Databases back in 1970, everybody was excited about this new cool technology that provides an elegant, disciplined and robust way of accessing data. But no matter how good or brilliant a technology may be, it remains technology - and that means it’s just a detail.
-
Clean Architecture Series: Business Rules and Use Cases
As mentioned in the previous articles, every Software System can be divided into Policies and Details. Describing behavior, the Policies are considered to be high-level while the Details, which concern how the Policies are actually implemented, are considered low-level. Ideally, the Clean Architecture should be seen more like a “Plugin Architecture” i.e. an Architecture describing that at the heart of the system lie the Business Rules, with lesser concerns being plugged into that system (from where the term Plugin comes from).
-
Clean Architecture Series: Overview
Clean Architecture represents a collection of patterns, practices, and principles used to create modern, high quality and elegant software systems that are simple to understand, flexible, testable and maintainable. Clean Architecture is a robust alternative to the traditional 3-layer, database-centric architecture, which has been used for decades and is known for its limitations.
subscribe via RSS