<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>restful apis on Kuldeep Pisda</title><link>https://kdpisda.in/tag/restful-apis/</link><description>Recent content in restful apis on Kuldeep Pisda</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sat, 01 Nov 2025 15:49:44 +0530</lastBuildDate><atom:link href="https://kdpisda.in/tag/restful-apis/index.xml" rel="self" type="application/rss+xml"/><item><title>A Guide to REST API Design Principles</title><link>https://kdpisda.in/a-guide-to-rest-api-design-principles/</link><pubDate>Sat, 01 Nov 2025 15:49:44 +0530</pubDate><guid>https://kdpisda.in/a-guide-to-rest-api-design-principles/</guid><description>&lt;p&gt;REST API design principles aren&amp;rsquo;t just abstract rules; they&amp;rsquo;re the architectural guardrails that keep your APIs scalable, maintainable, and predictable. When you follow these well worn paths—like using a uniform interface and keeping communication stateless—you end up building logical and consistent web services. Think of them as battle tested guidelines that prevent your system from imploding.&lt;/p&gt;
&lt;h2 id="the-night-an-api-flaw-almost-broke-production"&gt;The Night an API Flaw Almost Broke Production&lt;a class="heading-anchor" href="#the-night-an-api-flaw-almost-broke-production" aria-hidden="true" tabindex="-1"&gt;#&lt;/a&gt;
&lt;/h2&gt;
&lt;p&gt;It was a Tuesday night. A deployment that seemed completely routine went live, and within an hour, our server load started to spike—hard. The culprit? An API endpoint that looked fine on the surface but secretly violated a core REST principle we&amp;rsquo;d completely overlooked.&lt;/p&gt;</description></item></channel></rss>