<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Architecture on Jonayed Hossan Gazi</title><link>https://jonayed-hossan-gazi.github.io/tags/architecture/</link><description>Recent content in Architecture on Jonayed Hossan Gazi</description><image><title>Jonayed Hossan Gazi</title><url>https://jonayed-hossan-gazi.github.io/images/site/og-default.png</url><link>https://jonayed-hossan-gazi.github.io/images/site/og-default.png</link></image><generator>Hugo</generator><language>en-us</language><lastBuildDate>Fri, 05 Jun 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://jonayed-hossan-gazi.github.io/tags/architecture/index.xml" rel="self" type="application/rss+xml"/><item><title>A decade of code, zero forced migrations</title><link>https://jonayed-hossan-gazi.github.io/2026/05/decade-of-compatibility/</link><pubDate>Wed, 06 May 2026 00:00:00 +0000</pubDate><guid>https://jonayed-hossan-gazi.github.io/2026/05/decade-of-compatibility/</guid><description>Code written in 2013 still runs on Wapka today — unchanged alongside code from 2026. Here is how backward compatibility became a design principle, not an afterthought.</description></item><item><title>How Wapka's request router handles three eras simultaneously</title><link>https://jonayed-hossan-gazi.github.io/2026/05/request-router/</link><pubDate>Wed, 06 May 2026 00:00:00 +0000</pubDate><guid>https://jonayed-hossan-gazi.github.io/2026/05/request-router/</guid><description>A single web request arrives at Wapka. It could match a legacy WAP tag page, a Lua route, or a Native App. Here is the architecture that dispatches across three eras.</description></item><item><title>Real-time chat and WebSockets on shared hosting</title><link>https://jonayed-hossan-gazi.github.io/2026/05/real-time-features/</link><pubDate>Wed, 06 May 2026 00:00:00 +0000</pubDate><guid>https://jonayed-hossan-gazi.github.io/2026/05/real-time-features/</guid><description>Real-time chat, notifications, and live updates — running on shared hosting without dedicated servers. How Wapka handles WebSockets at scale.</description></item><item><title>Why Wapka runs on Lua — the architectural decision behind it</title><link>https://jonayed-hossan-gazi.github.io/2026/05/why-lua/</link><pubDate>Wed, 06 May 2026 00:00:00 +0000</pubDate><guid>https://jonayed-hossan-gazi.github.io/2026/05/why-lua/</guid><description>Choosing Lua for Wapka&amp;#39;s scripting engine wasn&amp;#39;t a compromise. It was the only correct engineering decision for a shared hosting platform at scale.</description></item><item><title>Why Wapka's compute costs are near zero</title><link>https://jonayed-hossan-gazi.github.io/2026/05/luajit-economics/</link><pubDate>Wed, 06 May 2026 00:00:00 +0000</pubDate><guid>https://jonayed-hossan-gazi.github.io/2026/05/luajit-economics/</guid><description>Why Wapka can offer server-side scripting for free. The numbers show how Lua via PHP LuaSandbox makes compute costs near zero on shared infrastructure.</description></item></channel></rss>