<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Swapnil Mahmud</title>
    <description>The latest articles on DEV Community by Swapnil Mahmud (@swapnil_mahmud).</description>
    <link>https://dev.to/swapnil_mahmud</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F1986509%2Fc9564e69-b8d3-4bab-95b3-ac72e981ca88.jpeg</url>
      <title>DEV Community: Swapnil Mahmud</title>
      <link>https://dev.to/swapnil_mahmud</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/swapnil_mahmud"/>
    <language>en</language>
    <item>
      <title>REST API</title>
      <dc:creator>Swapnil Mahmud</dc:creator>
      <pubDate>Wed, 04 Sep 2024 09:46:22 +0000</pubDate>
      <link>https://dev.to/swapnil_mahmud/types-of-apis-48f5</link>
      <guid>https://dev.to/swapnil_mahmud/types-of-apis-48f5</guid>
      <description>&lt;p&gt;&lt;strong&gt;REST (Representational State Transfer) API&lt;/strong&gt;&lt;br&gt;
&lt;strong&gt;Description:&lt;/strong&gt;&lt;br&gt;
The most common type of web API, RESTful APIs use HTTP methods (GET, POST, PUT, DELETE, PATCH) and follow stateless communication principles.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Common Use Cases:&lt;/strong&gt;&lt;br&gt;
Web services&lt;br&gt;
E-commerce applications&lt;br&gt;
Social media integrations&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Data Format:&lt;/strong&gt;&lt;br&gt;
JSON, XML&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Key Features:&lt;/strong&gt;&lt;br&gt;
Stateless: Each request from a client contains all necessary information. The server does not store any session state between requests.&lt;br&gt;
Simple and Flexible: Utilizes standard HTTP methods, with communication typically in JSON format.&lt;br&gt;
Resource-Based: Organized around "resources" (e.g., products, users, orders) accessed via URLs (e.g., /api/products).&lt;br&gt;
Real-Life Examples:&lt;br&gt;
Twitter API: Allows developers to interact with Twitter's data, such as retrieving tweets or posting new ones.&lt;br&gt;
GitHub API: Provides access to GitHub repositories, issues, and pull requests.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Note:[Stateless vs. Stateful ]&lt;/strong&gt;&lt;br&gt;
Stateless: Each request is independent. The server does not store any context between requests.&lt;br&gt;
Stateful: The server maintains context or state between client requests, often storing session information on the server. Stateful systems can track user interactions over time.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media.dev.to/cdn-cgi/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2F66q94696wsrbo5jdgkx2.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media.dev.to/cdn-cgi/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2F66q94696wsrbo5jdgkx2.png" alt="Image description" width="800" height="421"&gt;&lt;/a&gt;&lt;/p&gt;

</description>
    </item>
    <item>
      <title>Laravel | Throttling | Service Provider | Service Container</title>
      <dc:creator>Swapnil Mahmud</dc:creator>
      <pubDate>Mon, 02 Sep 2024 09:01:40 +0000</pubDate>
      <link>https://dev.to/swapnil_mahmud/laravel-throttling-service-provider-service-container-5g05</link>
      <guid>https://dev.to/swapnil_mahmud/laravel-throttling-service-provider-service-container-5g05</guid>
      <description>&lt;p&gt;&lt;strong&gt;&lt;em&gt;Throttling or Rate limiting&lt;/em&gt;&lt;/strong&gt;&lt;br&gt;
Throttling is a mechanism used to limit the number of requests that can be made to certain routes or controllers within a specific time period. This is often used to prevent abuse or excessive usage of certain endpoints, APIs, or resources.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;&lt;em&gt;Service Providers&lt;/em&gt;&lt;/strong&gt;&lt;br&gt;
Service providers are the central place of all Laravel application bootstrapping. Your own application, as well as all of Laravel's core services, are bootstrapped via service providers.&lt;br&gt;
mean by "bootstrapped"? In general, we mean registering things, including registering service container bindings, event listeners, middleware, and even routes. Service providers are the central place to configure your application.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;&lt;em&gt;Service container&lt;/em&gt;&lt;/strong&gt;&lt;br&gt;
The Laravel service container is a powerful tool for managing class dependencies and performing dependency injection.In the simplest way to understand service container, we can assume that it is a box that holds various components’ bindings, and they are served as needed throughout the application.&lt;/p&gt;

&lt;p&gt;[NOTE:]&lt;br&gt;
The service container is where your services are registered. Service providers provide services by adding them to the container.&lt;/p&gt;

</description>
      <category>laravel</category>
      <category>php</category>
      <category>service</category>
    </item>
  </channel>
</rss>
