<?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 MacWorks</title><link>https://macworks.dev/tags/architecture/</link><description>Recent content in Architecture on MacWorks</description><generator>Hugo</generator><language>en</language><atom:link href="https://macworks.dev/tags/architecture/index.xml" rel="self" type="application/rss+xml"/><item><title>Week 14 Summary</title><link>https://macworks.dev/docs/month/tech/weekly-2026-W14/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://macworks.dev/docs/month/tech/weekly-2026-W14/</guid><description>&lt;h1 id="engineering--scale--week-of-2026-03-28-to-2026-04-03"&gt;Engineering @ Scale — Week of 2026-03-28 to 2026-04-03&lt;a class="anchor" href="#engineering--scale--week-of-2026-03-28-to-2026-04-03"&gt;#&lt;/a&gt;&lt;/h1&gt;
&lt;h2 id="week-in-review"&gt;Week in Review&lt;a class="anchor" href="#week-in-review"&gt;#&lt;/a&gt;&lt;/h2&gt;
&lt;p&gt;The industry is moving past the novelty of generative AI, focusing instead on bounding autonomous agents with strict architectural contracts, standardizing machine-to-machine context layers, and pushing security enforcement to the absolute edge. Concurrently, legacy infrastructure assumptions—ranging from traditional LRU caching algorithms to deeply nested UI component trees—are failing under the weight of AI-driven traffic and massive data scale, forcing engineers to adopt zero-trust capability sandboxing and highly optimized, O(1) data access patterns.&lt;/p&gt;</description></item><item><title>Tech Company Blogs</title><link>https://macworks.dev/docs/week/tech/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://macworks.dev/docs/week/tech/</guid><description>&lt;h1 id="engineering--scale--week-of-2026-04-03-to-2026-04-10"&gt;Engineering @ Scale — Week of 2026-04-03 to 2026-04-10&lt;a class="anchor" href="#engineering--scale--week-of-2026-04-03-to-2026-04-10"&gt;#&lt;/a&gt;&lt;/h1&gt;
&lt;h2 id="week-in-review"&gt;Week in Review&lt;a class="anchor" href="#week-in-review"&gt;#&lt;/a&gt;&lt;/h2&gt;
&lt;p&gt;This week, the industry rapidly shifted from conversational AI paradigms to formal &amp;ldquo;Agentic Infrastructure,&amp;rdquo; prioritizing strict deterministic guardrails over massive, unstructured context windows. Top organizations are aggressively fracturing monolithic processes—whether it is breaking down massive LLM prompts into specialized sub-agents, federating sprawling databases, or shifting compute-heavy security mitigation entirely to the network edge—to manage the unbounded scaling demands of machine actors.&lt;/p&gt;</description></item><item><title>2026-04-03</title><link>https://macworks.dev/docs/archives/tech/tech-2026-04-03/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://macworks.dev/docs/archives/tech/tech-2026-04-03/</guid><description>&lt;details&gt;
&lt;summary&gt;Sources&lt;/summary&gt;
&lt;div class="markdown-inner"&gt;
&lt;ul&gt;

&lt;li&gt;&lt;a href="https://medium.com/feed/airbnb-engineering"&gt;Airbnb Engineering&lt;/a&gt;&lt;/li&gt;

&lt;li&gt;&lt;a href="https://aws.amazon.com/blogs/machine-learning/feed/"&gt;Amazon AWS AI Blog&lt;/a&gt;&lt;/li&gt;

&lt;li&gt;&lt;a href="https://aws.amazon.com/cn/blogs/architecture/feed/"&gt;AWS Architecture Blog&lt;/a&gt;&lt;/li&gt;

&lt;li&gt;&lt;a href="https://aws.amazon.com/blogs/opensource/feed/"&gt;AWS Open Source Blog&lt;/a&gt;&lt;/li&gt;

&lt;li&gt;&lt;a href="https://brett.trpstra.net/brettterpstra"&gt;BrettTerpstra.com&lt;/a&gt;&lt;/li&gt;

&lt;li&gt;&lt;a href="https://blog.bytebytego.com/feed"&gt;ByteByteGo&lt;/a&gt;&lt;/li&gt;

&lt;li&gt;&lt;a href="https://blog.cloudflare.com/rss/"&gt;CloudFlare&lt;/a&gt;&lt;/li&gt;

&lt;li&gt;&lt;a href="https://dropbox.tech/feed"&gt;Dropbox Tech Blog&lt;/a&gt;&lt;/li&gt;

&lt;li&gt;&lt;a href="https://engineering.fb.com/feed/"&gt;Facebook Code&lt;/a&gt;&lt;/li&gt;

&lt;li&gt;&lt;a href="https://github.blog/engineering.atom"&gt;GitHub Engineering&lt;/a&gt;&lt;/li&gt;

&lt;li&gt;&lt;a href="https://blog.google/innovation-and-ai/technology/ai/rss/"&gt;Google AI Blog&lt;/a&gt;&lt;/li&gt;

&lt;li&gt;&lt;a href="https://deepmind.google/blog/rss.xml"&gt;Google DeepMind&lt;/a&gt;&lt;/li&gt;

&lt;li&gt;&lt;a href="http://feeds.feedburner.com/GoogleOpenSourceBlog"&gt;Google Open Source Blog&lt;/a&gt;&lt;/li&gt;

&lt;li&gt;&lt;a href="https://www.hashicorp.com/blog/feed.xml"&gt;HashiCorp Blog&lt;/a&gt;&lt;/li&gt;

&lt;li&gt;&lt;a href="https://feed.infoq.com/?token=XQ47eEiAJqUtN8043NhEqJ6kZB8XallO"&gt;InfoQ&lt;/a&gt;&lt;/li&gt;

&lt;li&gt;&lt;a href="https://engineering.atspotify.com/feed/"&gt;Spotify Engineering&lt;/a&gt;&lt;/li&gt;

&lt;li&gt;&lt;a href="https://www.microsoft.com/en-us/research/feed/"&gt;Microsoft Research&lt;/a&gt;&lt;/li&gt;

&lt;li&gt;&lt;a href="https://hacks.mozilla.org/feed/"&gt;Mozilla Hacks&lt;/a&gt;&lt;/li&gt;

&lt;li&gt;&lt;a href="https://netflixtechblog.com/feed"&gt;Netflix Tech Blog&lt;/a&gt;&lt;/li&gt;

&lt;li&gt;&lt;a href="http://feeds.feedburner.com/nvidiablog"&gt;NVIDIA Blog&lt;/a&gt;&lt;/li&gt;

&lt;li&gt;&lt;a href="http://feeds.feedburner.com/oreilly/radar/atom"&gt;O&amp;#39;Reilly Radar&lt;/a&gt;&lt;/li&gt;

&lt;li&gt;&lt;a href="https://openai.com/news/rss.xml"&gt;OpenAI Blog&lt;/a&gt;&lt;/li&gt;

&lt;li&gt;&lt;a href="https://developers.soundcloud.com/blog/blog.rss"&gt;SoundCloud Backstage Blog&lt;/a&gt;&lt;/li&gt;

&lt;li&gt;&lt;a href="https://stripe.com/blog/feed.rss"&gt;Stripe Blog&lt;/a&gt;&lt;/li&gt;

&lt;li&gt;&lt;a href="https://rsshub.bestblogs.dev/deeplearning/the-batch"&gt;The Batch | DeepLearning.AI | AI News &amp;amp; Insights&lt;/a&gt;&lt;/li&gt;

&lt;li&gt;&lt;a href="https://blog.dropbox.com/feed"&gt;The Dropbox Blog&lt;/a&gt;&lt;/li&gt;

&lt;li&gt;&lt;a href="https://github.blog/feed/"&gt;The GitHub Blog&lt;/a&gt;&lt;/li&gt;

&lt;li&gt;&lt;a href="https://medium.com/feed/netflix-techblog"&gt;The Netflix Tech Blog&lt;/a&gt;&lt;/li&gt;

&lt;li&gt;&lt;a href="https://blogs.microsoft.com/feed/"&gt;The Official Microsoft Blog&lt;/a&gt;&lt;/li&gt;

&lt;li&gt;&lt;a href="https://vercel.com/atom"&gt;Vercel Blog&lt;/a&gt;&lt;/li&gt;

&lt;li&gt;&lt;a href="https://engineeringblog.yelp.com/feed.xml"&gt;Yelp Engineering and Product Blog&lt;/a&gt;&lt;/li&gt;

&lt;/ul&gt;
&lt;/div&gt;
&lt;/details&gt;


&lt;h1 id="engineering--scale--2026-04-03"&gt;Engineering @ Scale — 2026-04-03&lt;a class="anchor" href="#engineering--scale--2026-04-03"&gt;#&lt;/a&gt;&lt;/h1&gt;
&lt;h2 id="signal-of-the-day"&gt;Signal of the Day&lt;a class="anchor" href="#signal-of-the-day"&gt;#&lt;/a&gt;&lt;/h2&gt;
&lt;p&gt;GitHub&amp;rsquo;s architectural rewrite of their PR diff view demonstrates that scaling complex React applications requires abandoning small, heavily-abstracted components in favor of O(1) data access patterns, top-level event delegation, and lazy state rendering. By stripping out redundant &lt;code&gt;useEffect&lt;/code&gt; hooks and shifting to Map-based selectors, they cut memory usage by 50% and improved Interaction to Next Paint (INP) by 78% for massive pull requests.&lt;/p&gt;</description></item></channel></rss>