Nx Caching Explained: Local and Remote Computation Caching
Learn how Nx caching hashes task inputs, restores outputs, and when local or remote caching saves CI time, and how to audit inputs and outputs so it stays correct.
14 min read
Archive
317 published
Learn how Nx caching hashes task inputs, restores outputs, and when local or remote caching saves CI time, and how to audit inputs and outputs so it stays correct.
14 min read
Learn how nx affected uses the project graph and base commit to scope CI runs, how to fix graph gaps, pick base SHAs, and when to run everything.
15 min read
Build a trustworthy dependency graph from runtime traces and declared data, use it to gate risky changes, spot unhealthy coupling, and retire endpoints safely.
13 min read
Learn to reduce build time by profiling the critical path first, then applying caching, parallelism and affected-only builds in order of measured payoff.
14 min read
Learn how the Nx project graph is built, cached and inspected, how it drives affected commands and caching, and how to debug missing or extra edges.
16 min read
Learn when a modular monolith beats microservices, how to enforce module boundaries, and which team size, deployment, and scaling needs justify a split.
18 min read
Learn what the API gateway pattern handles at the edge, how it differs from proxies and service meshes, when to adopt or skip it, and how to operate it.
13 min read
Learn how nx affected and the Nx cache cut CI time, how to configure inputs, outputs and diff bases correctly, and when remote caching is worth it.
14 min read
Model the cost of microservices as fixed platform cost plus per-service overhead plus infrastructure, then use it to decide if your next service is worth it.
13 min read
Choose between create-nx-workspace and nx init, read the workspace layout, inspect the project graph, and confirm caching works on your first Nx build.
12 min read
Learn what database per service means, why shared databases break microservices, and how sagas, outboxes and read models handle the costs it brings.
14 min read
Run a monolith to microservices migration as small, reversible extractions behind a routing layer, with data ownership, parity checks and clear exit points.
14 min read