<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>REST on laszlosimon.dev</title>
		<link>https://laszlosimon.dev/tags/rest/</link>
		<description>Recent content in REST on laszlosimon.dev</description>
		<generator>Hugo</generator>
		<language>en-us</language>
		
		
		
		
			<lastBuildDate>Sat, 05 Sep 2026 00:00:00 +0200</lastBuildDate>
		
			<atom:link href="https://laszlosimon.dev/tags/rest/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>When Microservices Should Stop Using REST</title>
				<link>https://laszlosimon.dev/articles/architecture/when-microservices-should-stop-using-rest/</link>
				<pubDate>Sat, 05 Sep 2026 00:00:00 +0200</pubDate>
				<guid>https://laszlosimon.dev/articles/architecture/when-microservices-should-stop-using-rest/</guid>
				<description>&lt;p&gt;REST is probably the most common communication mechanism between microservices.&lt;/p&gt;&#xA;&lt;p&gt;It is simple, familiar, easy to debug, and well supported by virtually every technology stack.&lt;/p&gt;&#xA;&lt;p&gt;But sometimes, using REST between services starts creating more problems than it solves.&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
