<<< GSA

• Dependency Injection in .NET

  • Dependency injection is the design pattern that allows us to inject the dependency into the class from the outer world rather than creating with in class. This will help us to create a loosely coupled applications so that it has provided greater maintainability, testability, and also reusability.

• IEnumerable vs IQueryable  in .NET

  • IQueryable is suitable for querying data from out-memory (like remote database, service) collections. Whereas IEnumerable is good for In-Memory Collection query. While querying data from a database, IQueryable executes a "select query" on server-side with all filters.

• Component vs Class (angular)

  • A component controls a part of the screen called a view, which is defined by a class that controls the view through its template. The component class interacts with the view through an API of properties and methods exposed by the component.

• Why to use Entity Framework Core?

  • EF Core can serve as an object-relational mapper (O/RM), which: Enables .NET developers to work with a database using .NET objects. Eliminates the need for most of the data-access code that typically needs to be written.

• Why to use Object Relational Mapping (ORM)?

  • Advantages of Using ORM Tools:

    • Handles the logic required to interact with databases. Improves security. ORM tools are built to eliminate the possibility of SQL injection attacks. You write less code when using ORM tools than with SQL.

• Why to use Clean Architecture .NET?

  • Clean Architecture: . NET core highly gets used by professionals to create applications based on a layered approach. It helps to reduce the dependability between business logic, use cases, and interface. And it supports in improving the testability, scalability, and app maintainability.

• SOLID Principles

  • Additionally, SOLID principles enable engineers to make designs easier to understand, maintain, and extend. Ultimately, using these design principles makes it easier for software engineers to avoid issues and to build adaptive, effective, and agile software.

• Why use SOLID Principles for Single Responsibility?

  • The argument for the single responsibility principle is relatively simple: it makes your software easier to implement and prevents unexpected side effects of future changes.

• Hash Map vs Hash Table

  • HashMap is non-syncronized and is not thread safe while HashTable is thread safe and is synchronized. HashMap allows one null key and values can be null whereas HashTable doesn't allow null key or value. HashMap is faster than HashTable. HashMap iterator is fail-safe where HashTable iterator is not fail-safe.

#AbdurRahimRatulAliKhan #ARRAK #Code #Programming #GlobalSoftwareArchitect #GSA #Viva

>>>