A practical guide to Dependency Injection and Inversion of Control in C#. Covers constructor injection, composition roots, lifetimes, containers, testing, and when DI is overkill.
ResultR v1.0.2 introduces the Match() method for functional-style pattern matching on results, making it easier to handle success and failure cases in a clean, expressive way.
A Modern Take on Request/Response Dispatching for .NET Hello World! I’ve been working on a side project that I wanted to share with you all. After MediatR went to a paid model, I’m sure you heard all about that?
A practical introduction to Microsoft Orleans and the Virtual Actor Model: what Grains and Silos are, how clustering works, and why Orleans is a great fit for scalable workflow-style systems.
The last of the SOLID Principles to cover is the letter D which is the Dependency Inversion Principle (DIP).
What is the Dependency Inversion Principle (DIP)? The Dependency Inversion Principle (DIP) states that “Depend on abstraction, not on concretions".
The fourth of the SOLID Principles to cover is the letter I which is the Interface Segregation Principle (ISP).
What is the Interface Segregation Principle (ISP)? The Interface Segregation Principle (ISP) states that “Clients should not be forced to depend upon interfaces that they do not use".
The third of the SOLID Principles to cover is the letter L which is the Liskov Substitution Principle (LSP).
What is the Liskov Substitution Principle (LSP)? The Liskov Substitution Principle (LSP) states that “Derived classes must be substitutable for their base classes".
The second of the SOLID Principles to cover is the letter O which is the Open-Closed Principle (OCP).
What is the Open-Closed Principle (OCP)? The Open-Closed Principle (OCP) states that “You should be able to extend a classes behavior, without modifying".