Architecture - Tag - fds-boardhttps://blog.fdsboard.com/tags/architecture/Architecture - Tag - fds-boardHugo -- gohugo.ioenFri, 13 Mar 2026 00:00:00 +0000Killing the if/else Hydra: Strategy Pattern for Dual Data Sources in a Next.js Apphttps://blog.fdsboard.com/architecture/datasource-strategy-pattern/Fri, 13 Mar 2026 00:00:00 +0000Jinze(Jerry) Zhouhttps://blog.fdsboard.com/architecture/datasource-strategy-pattern/1. The General Problem

The shape of this problem is generic: M consumer call sites need N data types, and each data type can be produced by more than one independent upstream source, each with its own event or payload shape. Left to grow organically, the naive fix is a fallback branch at every call site — an M × N × (source count) surface area, where each branch also has to encode which source to trust first and how to resolve partial failures.

]]>