CodeNXT Lab · Journal
Journal.
Architecture decisions and the failure modes that produced them. Written while the work was happening, not reconstructed afterwards.
-
09 Jul 2026 · 7 min read
A multi-tenant SaaS application lets several organizations share one software platform while their data and permissions stay separate. The engineering problem is holding that isolation, and the performance that goes with it, as the tenant count grows.
-
09 Jul 2026 · 18 min read
A queue system separates work from user interactions by processing tasks asynchronously. Reliable design comes from four guarantees: delivery, ordering, retry behaviour, and operational visibility. The technology is chosen after those are settled.
-
09 Jul 2026 · 7 min read
REST and RPC are two different approaches to designing application programming interfaces. Neither replaces the other. The best choice depends on the communication patterns, client requirements, system boundaries, and long-term maintenance goals.
-
09 Jul 2026 · 7 min read
Cloudflare Workers allow applications to execute close to users by running JavaScript and WebAssembly workloads on a globally distributed edge network. While this dramatically reduces network latency for many workloads, it also introduces execution constraints that influence software architecture.
-
09 Jul 2026 · 8 min read
SQLite and PostgreSQL solve different engineering problems, and neither is universally better. The right choice follows from workload characteristics, deployment architecture, write patterns, and operational complexity.
-
09 Jul 2026 · 7 min read
We treat programming languages as engineering tools. At CodeNXT Lab we select Go when its strengths fit the operational requirements of a system.