<aside> 🤲🏻

بِسْمِ اللَّهِ الرَّحْمَٰنِ الرَّحِيمِ

وَأَنْ لَيْسَ لِلْإِنْسَانِ إِلَّا مَا سَعَىٰ (39) وَأَنَّ سَعْيَهُ سَوْفَ يُرَىٰ (40) ثُمَّ يُجْزَاهُ الْجَزَاءَ الْأَوْفَىٰ (41) وَأَنَّ إِلَىٰ رَبِّكَ الْمُنْتَهَىٰ (42)

</aside>

📌 My personal accounts links

<aside> 📌

What is a ASP.NET Core ?

is a modern, fast, and cross-platform framework by Microsoft for building web apps and APIs. It works on Windows, Linux, and macOS and lets you create:

• Websites
• APIs (for mobile apps or other services)
• Real-time apps (like chat apps)

It's powerful, open-source, and great for building high-performance, scalable apps.

</aside>

<aside> 🚨

How ASP.NET Core Differs from ASP.NET?

</aside>

<aside> 💡

From Where Web API Come ?

In the past, if you wanted to share functionality or logic between applications, you would:

• Create a Class Library (DLL) in .NET.
• Add a Reference to that DLL in your main application.
• Directly use the classes and methods provided by the DLL.

📌 Limitations of the Old Approach:

1. Local Access Only: The DLL had to be physically present on the same machine or network.
2. Platform Dependency: Typically limited to applications built with the same technology stack (e.g., .NET apps).
3. Tight Coupling: Changes to the DLL required redeployment to all consuming applications.

🌐 The Rise of Web API (Modern Approach):

Web API is essentially the same concept as your old Class Library but exposed over HTTP via a web server. This allows it to be accessed from anywhere using a URL or domain, like:

https://myweb.com/api/data

✅ Why Web APIs Became Popular:

1. Platform Independence: Any application (web, mobile, desktop) can access the API using HTTP.
2. Global Accessibility: APIs hosted on a web server can be accessed from anywhere with an internet connection.
3. Scalability: Web APIs can be scaled independently of the consuming applications.
4. Security & Authentication: APIs can be protected using modern techniques (JWT, OAuth, API Keys).
5. Standard Communication Protocols: Uses standard protocols like HTTP, JSON, and XML, making it flexible for various clients.

🚀 How It Works:

1. Create a Web API using ASP.NET Core.
2. Deploy the API to a web server (IIS, Nginx, Azure, etc.).
3. Access the API using a URL or domain (e.g., https://example.com/api/data).
4. Consume the API from any application using HTTP requests (GET, POST, PUT, DELETE).

</aside>