
		<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
			<channel>
				<title>José David Baena – Distributed Systems Engineer</title>
				<link>https://josedavidbaena.com</link>
				<description>Production notes and source-backed analysis on distributed systems, messaging infrastructure, open-source internals, and model engineering.</description>
				<language>en-us</language>
				<managingEditor>josedab@gmail.com (José David Baena)</managingEditor>
				<webMaster>josedab@gmail.com (José David Baena)</webMaster>
				<lastBuildDate>Tue, 28 Jul 2026 00:00:00 GMT</lastBuildDate>
				<atom:link href="https://josedavidbaena.com/tags/architecture/feed.xml" rel="self" type="application/rss+xml"/>
				
		<item>
			<guid>https://josedavidbaena.com/blog/kimi-k3/02-architecture-kda-attnres-experts</guid>
			<title>Inside Kimi K3: How KDA, AttnRes, and 896 Experts Work</title>
			<link>https://josedavidbaena.com/blog/kimi-k3/02-architecture-kda-attnres-experts</link>
			<description>Trace Kimi K3&#39;s 69 KDA layers, 24 gated MLA layers, Attention Residuals, and 896 experts without overstating what released artifacts prove.</description>
			<pubDate>Tue, 28 Jul 2026 00:00:00 GMT</pubDate>
			<author>josedab@gmail.com (José David Baena)</author>
			<category>kimi-k3</category><category>architecture</category><category>attention</category><category>mixture-of-experts</category><category>machine-learning</category>
		</item>
	
		<item>
			<guid>https://josedavidbaena.com/blog/exploration-redpanda/architecture-overview</guid>
			<title>Redpanda Architecture: Kafka Outside, Shards Inside</title>
			<link>https://josedavidbaena.com/blog/exploration-redpanda/architecture-overview</link>
			<description>Redpanda presents Kafka APIs outside while sharded C++, per-partition Raft, and raft0 define the implementation and operational boundaries inside.</description>
			<pubDate>Fri, 08 May 2026 00:00:00 GMT</pubDate>
			<author>josedab@gmail.com (José David Baena)</author>
			<category>redpanda</category><category>kafka</category><category>architecture</category><category>seastar</category><category>distributed-systems</category>
		</item>
	
		<item>
			<guid>https://josedavidbaena.com/blog/kafka-compatibility-portability-boundaries</guid>
			<title>Kafka Compatibility Is Not the Same as Portability</title>
			<link>https://josedavidbaena.com/blog/kafka-compatibility-portability-boundaries</link>
			<description>Kafka client compatibility lowers rewrite cost. Portability still depends on semantics, state, durable authority, operations, migration, and contract.</description>
			<pubDate>Fri, 06 Mar 2026 00:00:00 GMT</pubDate>
			<author>josedab@gmail.com (José David Baena)</author>
			<category>kafka</category><category>streaming</category><category>compatibility</category><category>architecture</category><category>migrations</category>
		</item>
	
		<item>
			<guid>https://josedavidbaena.com/blog/kafka-consumer-groups-platform-infrastructure</guid>
			<title>Kafka Consumer Groups Are Platform Infrastructure</title>
			<link>https://josedavidbaena.com/blog/kafka-consumer-groups-platform-infrastructure</link>
			<description>A platform contract should own Kafka client lifecycle, migration, and observability without pretending it can own application side effects.</description>
			<pubDate>Fri, 06 Feb 2026 00:00:00 GMT</pubDate>
			<author>josedab@gmail.com (José David Baena)</author>
			<category>kafka</category><category>distributed-systems</category><category>consumer-groups</category><category>platform-engineering</category><category>architecture</category>
		</item>
	
		<item>
			<guid>https://josedavidbaena.com/blog/mermaid-nextjs-journey/mermaid-diagrams-three-architectures-one-solution</guid>
			<title>Three Architectures, One Solution: Building a Mermaid.js Diagram System</title>
			<link>https://josedavidbaena.com/blog/mermaid-nextjs-journey/mermaid-diagrams-three-architectures-one-solution</link>
			<description>Three Mermaid-in-Next.js architectures, one that shipped. Index post for a 3-part case study on build-time rendering, over-engineering, and deletion.</description>
			<pubDate>Mon, 20 Oct 2025 00:00:00 GMT</pubDate>
			<author>josedab@gmail.com (José David Baena)</author>
			<category>nextjs</category><category>mermaid</category><category>architecture</category><category>performance</category><category>case-study</category><category>pragmatic-engineering</category>
		</item>
	
		<item>
			<guid>https://josedavidbaena.com/blog/tiny-language-models/tiny-llm-case-studies-production</guid>
			<title>Tiny LLM Deployment Patterns: Architecture Blueprints from Published Benchmarks</title>
			<link>https://josedavidbaena.com/blog/tiny-language-models/tiny-llm-case-studies-production</link>
			<description>Deployment patterns for tiny LLMs in healthcare, legal, manufacturing, and edge—grounded in published benchmarks from Microsoft, Apple, and MLPerf.</description>
			<pubDate>Mon, 13 Oct 2025 00:00:00 GMT</pubDate>
			<author>josedab@gmail.com (José David Baena)</author>
			<category>machine-learning</category><category>deployment-patterns</category><category>production</category><category>benchmarks</category><category>architecture</category>
		</item>
	
		<item>
			<guid>https://josedavidbaena.com/blog/tiny-language-models/tiny-llm-architecture-comparison</guid>
			<title>Tiny LLM Architecture Comparison: TinyLlama vs Phi-2 vs Gemma vs MobileLLM</title>
			<link>https://josedavidbaena.com/blog/tiny-language-models/tiny-llm-architecture-comparison</link>
			<description>Seven tiny models, one decision. Phi-2 wins on reasoning (56.7% MMLU). MobileLLM on speed (120 tok/s). Qwen on multilingual. Match constraints to model.</description>
			<pubDate>Sat, 20 Sep 2025 00:00:00 GMT</pubDate>
			<author>josedab@gmail.com (José David Baena)</author>
			<category>machine-learning</category><category>llm</category><category>architecture</category><category>benchmarks</category><category>comparison</category>
		</item>
	
			</channel>
		</rss>
	