-
Middleware in .NET? In ASP.NET Core, a middleware is a component in the request/response pipeline that handles: Middlewares can: Middleware Execution Flow: Request -> Middleware A -> Middleware B -> Middleware C -> Controller<- Post-C -> Post-B -> Post-A -> Response Code before _next() runs on the way in Code after _next() runs on the
-
When starting a new .NET project, many developers default to Entity Framework (EF) — and for good reason. EF Core is robust, feature-rich, and beautifully abstracts away most database complexity. But here’s the problem: using Entity Framework everywhere can easily overload your application with unnecessary memory consumption, query overhead, and sluggish performance, especially for simple
-
Transitioning from a senior developer or lead role to a Technical Architect is a natural progression for many experienced professionals. As a Technical Architect, you’ll be responsible for designing scalable, secure, and efficient systems while leading technical teams and making high-level decisions. If you’re an experienced .NET professional with 10+ years of experience, this guide will provide
-
General Guidelines that can guide your class structure and relations. Definition of Design Principles in Programming Design principles in programming refer to a set of guidelines and advice’s and best practices that help software developers create structured, maintainable, and efficient code. These principles aim to improve code readability, facilitate collaboration among developers, and enhance the
-
How IEnumerable<T> Injection Works in .NET Core When you register multiple implementations of an interface in the DI container, the framework automatically groups these implementations into an IEnumerable<T> when you inject them. Step-by-Step Explanation: Why It Works Practical Implications Summary In .NET Core, when you inject an IEnumerable<T> of an interface, the DI container automatically
-
Category Patterns Structural( Focuses on Inner parts of the system) MVC, Layered Architecture, Client-Server Architecture, Pipe-and-Filter Architecture, Hexagonal Architecture, Microkernel Architecture Behavioral Event-Driven Architecture, CQRS, Event Sourcing Landscape(Focuses on big picture of the systems) Microservices Architecture, Service-Oriented Architecture, Serverless Architecture, Domain-Driven Design 1. Structural Patterns Structural patterns define the organization and static components of a
-
Message brokers are essential for enabling communication between different systems and applications. Here are some of the different types of message brokers you can use, including those available in Azure: Types of Message Brokers Key Features to Consider Use Cases
-
Defines an interface for creating an object, but lets subclasses decide which class to instantiate. Understanding the Factory Method Pattern Imagine a logging system where you want to log messages to different targets (e.g., console, file, database). You want to make the logging mechanism flexible and easily configurable.. This is essentially the Factory Method pattern.
-
What are Design Patterns? Think of design patterns as pre-designed blueprints for solving common software design problems. They are reusable solutions to recurring design challenges. They are not concrete implementations but rather general guidelines that can be adapted to different scenarios. Categorizing Design Patterns Design patterns are typically categorized into three main groups: Creational Design
-
Azure offers a comprehensive range of cloud computing services, encompassing various deployment models to suit different organizational needs. These models include the Public Cloud, Private Cloud, and Hybrid Cloud, each with its unique characteristics, benefits, and drawbacks. Below is an overview of each model with Azure-specific examples: Public Cloud Definition: The public cloud model involves
-
Subscribe
Subscribed
Already have a WordPress.com account? Log in now.
NARESH ASKANI 