Projects and articles related to Architecture.
Apr 23, 2026
Our platforms were stable and revenue-positive, but scale exposed retry storms, fanout bottlenecks, and noisy incidents. Here is how we decided when to add BullMQ and RabbitMQ, what we measured, and what changed.
Apr 22, 2026
Platforms like LibreChat give you a production-ready chat UI, multi-model routing, and built-in Langfuse integration. Custom agent frameworks give you reactive UI, transactional tool execution, and full rendering control. Here is how I decide between them across four different products.
Apr 21, 2026
Microfrontends are not a default architecture. Here is how I decided to migrate from a frontend monolith to domain-based frontend apps, what changed in deployment speed and cost, and when this approach is worth it.
Apr 19, 2026
Part 1 of my portfolio AI series: Convex agent component design, RAG fundamentals, OpenAI vs Google provider testing, streaming UX, and how the frontend chat bubble and /admin/ai tooling live inside one reusable AI plugin.
Apr 18, 2026
Part 2 of my portfolio AI series: concrete eval results, ClickHouse monitoring signals, optimization decisions, recursion guardrails, and the measured before/after impact.
Apr 17, 2026
A practical guide to embedding dimensions using our Portal support retrieval pipeline and shared support/AI components: how dimension choice changes quality, latency, storage, and migration strategy.
Apr 16, 2026
Most developers use AI to generate throwaway code for every new project. I use it to build CLIs, agent skills, test harnesses, and plugin scaffolds — repeatable infrastructure that compounds. Here is why spinning up a fresh agent session per task, with pre-built tools and context, beats ad-hoc prompting every time.
Apr 14, 2026
Our AI scanner said a page violated WCAG 2.4.7 — but it cited the wrong success criterion. RAG fixed the hallucination problem by grounding every AI claim in the actual specification, with retrieval metrics that prove the system works.
Apr 12, 2026
Both Cloudflare Workers and Convex let you run server-side code without managing servers. But they solve fundamentally different problems. After running both in production, here is when I reach for each one — and where they overlap more than you might expect.
Apr 10, 2026
Every system in the LaunchThat ecosystem uses classical software engineering patterns — Strategy, Observer, Adapter, State Machine — and formal data structures. Here is how GoF patterns, SOLID principles, and CS fundamentals show up in production code.
Apr 9, 2026
Both .NET and Convex can power production backends. After building multi-tenant SaaS platforms, high-performance APIs, and real-time dashboards across both, here is how I decide which one fits — and when the answer is both.
Apr 8, 2026
We moved off Vercel onto a 128GB bare-metal server. Each client now gets their own frontend containers, their own Convex backend instance, and their own database backups — orchestrated with Kubernetes and Helm. Here is how we got here and what we learned about owning infrastructure.
Apr 7, 2026
Switching from Drizzle/Postgres to Convex collapsed the frontend-backend gap, doubled development speed, and let me cancel $230/month in third-party services. Here is how the migration worked and what it unlocked.
Apr 6, 2026
I replaced a WordPress multisite with a custom Next.js app backed by Postgres. Load times dropped from 8 seconds to under 2. But the platform was still fractured across a dozen third-party services, and every schema change was a deployment risk.
Apr 4, 2026
Seven years ago I set out to build a multi-tenant platform on WordPress Multisite. All client data lived in one database, third-party glue held everything together, and a $100/mo host still could not keep up. Here is what I learned — and why I had to leave WordPress behind.
Apr 3, 2026
Neither ClickHouse nor Convex alone solves the trading chart problem. Here is how we split candle data between a columnar time-series engine and a real-time document database — and why the boundary sits exactly where it does.
Apr 2, 2026
We kept creating new repos for every project. Shared code drifted, configs diverged, and a single bug fix became a multi-day coordination exercise. Here is how a Turborepo monorepo fixed all of it.
Mar 30, 2026
Every customer wanted something different. The CRM customer needed contacts. The LMS customer needed courses. We were shipping bloated software that served nobody well. Here is how plugins fixed it.
Mar 29, 2026
A customer asked for Monday.com integration. We could have hard-coded it into the core. Instead, we built a plugin system — and 18 months later we have 34 plugins serving 27 apps.
