Contact Us

Popular posts from this blog

Send API POST Request in MS SQL Server

To send an API POST request in MS SQL Server using multipart/form-data, you can use the following T-SQL code: Example of content type : multipart/form-data SQL DECLARE @url VARCHAR(200) = 'https://example.com/api'; DECLARE @boundary VARCHAR(50) = '---------------------------' + CAST(NEWID() AS VARCHAR(36)); DECLARE @param1Name VARCHAR(50) = 'name'; DECLARE @param1Value VARCHAR(50) = 'John Doe'; DECLARE @param2Name VARCHAR(50) = 'email'; DECLARE @param2Value VARCHAR(50) = 'johndoe@example.com'; DECLARE @param3Name VARCHAR(50) = 'file'; DECLARE @param3Value VARBINARY(MAX) = (SELECT BulkColumn FROM OPENROWSET(BULK 'C:\path\to\file.txt', SINGLE_BLOB) AS x); DECLARE @param4Name VARCHAR(50) = 'description'; DECLARE @param4Value VARCHAR(200) = 'This is a sample file'; DECLARE @formData NVARCHAR(MAX) = N'--' + @boundary + CHAR(13) + CHAR(10) + ...
Read more

Tightly Coupled and Loosely Coupled in .NET Core with example

In .NET Core, tight coupling and loose coupling refer to the way software components are designed and connected to each other. Tight coupling in .NET Core means that two or more software components are highly dependent on each other, making it difficult to modify or replace one component without affecting the others. This can lead to maintenance and testing challenges, as well as reduced flexibility and scalability. Loose coupling in .NET Core, on the other hand, means that software components are designed to be independent and have minimal interdependence. This is achieved by using interfaces, dependency injection, and other techniques to reduce the direct dependencies between components. Loose coupling allows components to be more easily replaced, modified, or extended without affecting the rest of the system. Summary, loose coupling is generally preferred in .NET Core because it makes software more flexible, maintainable, and scalable. Advant...
Read more

Configure the API gateway in Microservices Architecture with example in .NET Core

API Gateway in Microservices Architecture In a microservices architecture, an API Gateway is a layer that sits between clients and the microservices that provide the necessary functionalities. It acts as a single entry point for all client requests and handles communication between the clients and the underlying microservices. The API Gateway serves as a mediator between the client and the backend services. It receives incoming requests from clients and routes them to the appropriate microservice. It also handles authentication, authorization, load balancing, and other cross-cutting concerns such as rate limiting, caching, and request/response transformation. By providing a single entry point and a unified interface for clients, the API Gateway simplifies client access to the system and helps to decouple the client code from the underlying microservices. It also provides a central point for monitoring and logging of all the incoming requests, making it easier to identify and troublesho...
Read more

Domain Driven Design (DDD) in .NET Core

Domain-Driven Design (DDD) is an approach to software development that emphasizes the importance of the business domain in the software design process. It is a set of principles and practices aimed at building software systems that are aligned with the business needs and requirements. The main idea behind DDD is to create a shared understanding of the domain model between the domain experts (business stakeholders) and the software developers. This is achieved by using a common language and a set of tools that allow for the domain model to be explicitly represented and manipulated in code. In DDD, the domain model is the central focus of the software design process. It is a representation of the core business concepts and rules that govern the behavior of the system. The domain model is expressed in code using object-oriented programming techniques, and it serves as the backbone of the software system. DDD also introduces several design patterns and ...
Read more

How To Setup Angular 10 Environment On Windows

If you are new to angular, Please follow below steps to setup angular 10 in your windows environment.  Download and Install node.js in your windows environment. Download Node JS   We need code editor tool to create and run the angular projects. We have best tools to choose from online.  Visual Studio Code is Open Source Tool, Download and Install VSCode . WebStorm is Premium Tool, To Download and Install WebStorm Tool   Once you have install above tools. We need to install Angular CLI latest version. To Install the Angular CLI in your windows environment. We have two ways to install. globally - npm install -g @angular/cli@latest  In upcoming posts I will explain you two types: a) globally   b) locally.  Now Angular Setup is ready in your windows environment, so you can create the projects and libraries.
Read more

Angular CLI Commands - Cheat Sheet

Image
Angular CLI (Command Line Interface) is one of the powerful tool that allows you to perform a lot of actions in an Angular project by using simple commands. We can use the CLI tool directly in a command shell, or indirectly through an interactive UI such as Angular Console.  The Best Advantage is that, can avoid manual process to create lot of stuff like create components, directives, feature modules, services... etc.  It automatically recompiles the source code files and refreshes the app in the browser.  Let's see, how to install CLI tool and what are those CLI commands. Installing the CLI is very quite easy. All we need to do, is to run the below command in Terminal or Console. It will install the CLI tool globally with respective version. Here we need to know two things before installing the CLI tool. We can install latest version or any version released by angular team based on your project need. Check the Versions list.✋ Angular CLI Setup  1. Globally - To ins...
Read more

Difference of High-Level Design (HLD) and Low-Level Design (LLD)

High-Level Design (HLD) and Low-Level Design (LLD) are software design concepts that are not specific to any programming language. However, to illustrate the differences between HLD and LLD, we can use C# programming language examples. Suppose we are designing a software system that involves creating a payment gateway application in C#.  Here are examples of HLD and LLD for this system: High-Level Design (HLD): Define the functional requirements of the payment gateway system, such as processing payment transactions, handling errors, and providing a user interface. Identify the non-functional requirements, such as performance, scalability, and security. Identify the key components of the payment gateway system, such as payment processing engine, database, user interface, and error handling. Create an architecture diagram that shows how these components will fit together to form the payment gateway system. In HLD, the focus is on defining the system's overall structure and architectu...
Read more

Clean Architecture in a C#

Clean Architecture is a software design pattern that separates the application into independent layers, where each layer has a specific responsibility and interacts with other layers through well-defined interfaces. The main goal of clean architecture is to create a flexible, testable, and maintainable software system. By following this architecture, we have created a flexible, testable, and maintainable software system. The domain layer is independent of any external dependencies and frameworks, making it easy to test and change without affecting other layers. The application layer contains the use cases or application-specific logic, which is decoupled from the infrastructure Here's an example of how to implement Clean Architecture in a C# project: 1. Domain Layer: This layer contains the business logic and domain-specific entities. It should be independent of any external dependencies and frameworks. C# ...
Read more

Implementing DIP (Dependency Inversion Principle) in .NET Core project

Dependency Inversion Principle (DIP) is one of the SOLID principles that states that high-level modules should not depend on low-level modules, instead both should depend on abstractions. In .NET Core, we can implement DIP using various techniques such as Dependency Injection, Inversion of Control (IoC), and Service Locator. Here's a simple example of how to implement DIP using Dependency Injection in a .NET Core project: By following below steps, we can implement DIP in our .NET Core project using Dependency Injection. 1. Define interfaces for the low-level modules (dependencies) that the high-level module needs to use. For example: public interface ILogger {     void Log( string message); } public interface IDataProvider {     string GetData(); } 2. Create implementations for these interfaces.  For example: public class FileLogger : ILogger {     public void Log( string message)     {         // cod...
Read more

RxJs Operators in Angular

RxJS (Reactive Extensions for JavaScript) is a library for reactive programming using Observables, which are a way to represent asynchronous data streams. RxJS provides a set of operators that can be used to transform, filter, combine, and manipulate these data streams. In RxJS, operators are functions that take one or more observables as input, and return a new observable. These operators can be chained together to create complex data stream transformations. RxJS operators have several advantages and disadvantages that are worth considering: Advantages: Composable : RxJS operators are composable, which means they can be combined in a variety of ways to create complex data stream transformations. This allows for a high degree of flexibility and modularity in reactive programming applications. Asynchronous : RxJS operators are designed to handle asynchronous data streams, which are common in modern web applications. This makes them well-suited for tasks like handling user input, making ...
Read more