<?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: Navinduuu</title>
    <description>The latest articles on DEV Community by Navinduuu (@navinduuu).</description>
    <link>https://dev.to/navinduuu</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.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4231872%2Ffb7f4249-9e9c-4ff7-8843-9c0a7f5ac78f.jpg</url>
      <title>DEV Community: Navinduuu</title>
      <link>https://dev.to/navinduuu</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/navinduuu"/>
    <language>en</language>
    <item>
      <title>Getting Started with WSO2 API Manager: A Quick Developer Guide</title>
      <dc:creator>Navinduuu</dc:creator>
      <pubDate>Sat, 07 Nov 2026 10:34:37 +0000</pubDate>
      <link>https://dev.to/navinduuu/getting-started-with-wso2-api-manager-a-quick-developer-guide-4ceg</link>
      <guid>https://dev.to/navinduuu/getting-started-with-wso2-api-manager-a-quick-developer-guide-4ceg</guid>
      <description>&lt;p&gt;Hello everyone! Lately, I have been researching various techniques for managing APIs as well as routing the backends properly. For all those who are developing applications and would like a good technique for controlling traffic, imposing rate limits and securing endpoints without having to create any middleware themselves, WSO2 API Manager is something worth exploring.&lt;/p&gt;

&lt;p&gt;What I intended was to present a brief yet comprehensive explanation on how this works and on how one can establish a proxy.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Why do I need an API Gateway?&lt;/strong&gt;&lt;br&gt;
If I have a frontend or mobile application that is calling more than one microservice directly, then I will soon be faced with a number of issues:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;API key management becomes an issue.&lt;/li&gt;
&lt;li&gt;Uncontrolled traffic could easily overload my backend infrastructure.&lt;/li&gt;
&lt;li&gt;Usage accounting for various applications becomes harder.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;An API gateway sits right in the middle. It handles the authentication and rate limits before a request ever hits your actual services.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Configuring an Initial API Gateway&lt;/strong&gt;&lt;br&gt;
In case you are testing this locally or configuring your initial project setup, then this is the process that will be involved:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;&lt;p&gt;Starting the Publisher: Access the WSO2 API Publisher console.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Create an API: Provide a name for the API (for example, MyTestAPI) and specify a context path (such as /api/v1) and the endpoint URL of your API.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Enabling Security: Enable the API Key or OAuth2 security to ensure that requests which are not authorized are denied access right away.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Setting Up the Rate Limiting: Select any basic plan (for instance, 50 calls per minute).&lt;/p&gt;&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;&lt;strong&gt;Trying It Out&lt;/strong&gt;&lt;br&gt;
After deploying your API to the gateway, you can start testing it out straight from your terminal with curl:&lt;/p&gt;

&lt;p&gt;curl -X GET "&lt;a href="https://localhost:9443/api/v1/1.0.0/users" rel="noopener noreferrer"&gt;https://localhost:9443/api/v1/1.0.0/users&lt;/a&gt;" \&lt;br&gt;
  -H "Authorization: Bearer YOUR_ACCESS_TOKEN"&lt;/p&gt;

&lt;p&gt;If all is done properly, then the gateway will verify your access token and forward the request to your backend API service.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Final Thoughts&lt;/strong&gt;&lt;br&gt;
Having to set up a gateway may seem unnecessary for a small-scale side project, but if your application is multi-service or intended to go into production, having that central gateway is really going to save you some trouble. &lt;/p&gt;

&lt;p&gt;&lt;strong&gt;If you want to try out WSO2, let me know what you think in the comments below!&lt;/strong&gt;&lt;/p&gt;

</description>
      <category>wso2</category>
      <category>apimanagement</category>
    </item>
  </channel>
</rss>
