<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Uuid on cloudmato.com</title><link>https://cloudmato.com/tags/uuid/</link><description>Recent content in Uuid on cloudmato.com</description><generator>Hugo -- gohugo.io</generator><language>en</language><managingEditor>cloudmato.com</managingEditor><webMaster>cloudmato.com</webMaster><lastBuildDate>Thu, 04 Jun 2026 22:06:34 +0530</lastBuildDate><atom:link href="https://cloudmato.com/tags/uuid/index.xml" rel="self" type="application/rss+xml"/><item><title>UUID vs Sequential IDs: What, Why, and Which to Pick</title><link>https://cloudmato.com/posts/uuid-vs-sequential-ids-explained/</link><pubDate>Thu, 04 Jun 2026 22:06:34 +0530</pubDate><author>cloudmato.com</author><guid>https://cloudmato.com/posts/uuid-vs-sequential-ids-explained/</guid><description>&lt;p&gt;You expose an API endpoint like &lt;code&gt;/api/orders/1042&lt;/code&gt;. That integer tells anyone listening — a competitor, an attacker, a curious user — exactly how many orders you have. Change the number to 1041, you get the previous order. Change it to 1, you get the very first one. No auth bypass needed. The ID itself is the information leak.&lt;/p&gt;
&lt;p&gt;That&amp;rsquo;s the sequential ID problem in one paragraph. UUID exists to fix it — and a few other things that matter at scale.&lt;/p&gt;</description></item></channel></rss>