<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Web-Development on Compile My Mind</title>
		<link>https://www.compilemymind.com/tags/web-development/</link>
		<description>Recent content in Web-Development on Compile My Mind</description>
		<generator>Hugo</generator>
		<language>en</language>
		
		
		
		
			<lastBuildDate>Sun, 20 Sep 2026 22:14:45 +0300</lastBuildDate>
		
			<atom:link href="https://www.compilemymind.com/tags/web-development/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>What Is a REST API and How Does It Work?</title>
				<link>https://www.compilemymind.com/posts/what-is-a-rest-api/</link>
				<pubDate>Sun, 20 Sep 2026 22:14:45 +0300</pubDate>
				<guid>https://www.compilemymind.com/posts/what-is-a-rest-api/</guid>
				<description>&lt;p&gt;A mobile app shows an order. The customer taps &lt;strong&gt;Cancel&lt;/strong&gt;, a request crosses the internet, and a moment later the screen says the order is cancelled.&lt;/p&gt;&#xA;&lt;p&gt;That small interaction hides several decisions. How does the app identify the order? How does it express “cancel”? Does the server remember earlier requests? Can a cache reuse the response? What tells the app which action is possible next?&lt;/p&gt;&#xA;&lt;p&gt;People often compress all of those decisions into one sentence: “The app calls a REST API.” Then REST gets reduced to JSON over HTTP, or to a naming convention for URLs.&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
