<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Architecture on Aiman Aizuddin</title><link>https://aimanaizuddin.com/tags/architecture/</link><description>Recent content in Architecture on Aiman Aizuddin</description><generator>Hugo</generator><language>en-MY</language><copyright>Copyright © 2026, Aiman Aizuddin.</copyright><lastBuildDate>Fri, 04 Sep 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://aimanaizuddin.com/tags/architecture/index.xml" rel="self" type="application/rss+xml"/><item><title>Designing Ledgerlane's URLs before the database</title><link>https://aimanaizuddin.com/build-log/designing-ledgerlane-urls-before-the-database/</link><pubDate>Fri, 04 Sep 2026 00:00:00 +0000</pubDate><guid>https://aimanaizuddin.com/build-log/designing-ledgerlane-urls-before-the-database/</guid><description>&lt;p&gt;For Ledgerlane, the URL plan was not a finishing detail. I treated it as an early piece of product architecture: decide where each version of the product lives before deciding how its data is allowed to move.&lt;/p&gt;
&lt;h2 id="the-map"&gt;The map&lt;/h2&gt;
&lt;p&gt;The project now has a clear purpose for each environment:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;a public marketing site;&lt;/li&gt;
&lt;li&gt;a production workspace, connected to real data for approved users;&lt;/li&gt;
&lt;li&gt;a public demonstration with fictional, browser-local records; and&lt;/li&gt;
&lt;li&gt;a private testing environment with synthetic data and restricted access.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;This separation shapes development. A feature can be tested in an environment designed for it, while a public demo stays safe to share and production remains focused on the real workflow. More importantly, it makes the data boundary visible in the product architecture instead of relying on a developer remembering which settings are safe.&lt;/p&gt;</description></item></channel></rss>