$ Pulse · Tech Stack

Genuine hands-on Azure serverless experience — the stated purpose of this piece, not Python pretending to be Node.

## TECH_STACK

Layer	Choice	Why
Frontend	Next.js / React	Same stack as every other page on this site — no separate frontend deploy for this one piece.
Backend	Azure Functions, Node.js, Flex Consumption	HTTP-triggered, anonymous-auth — the stack I wanted genuine hands-on time with, proving real Node.js/Azure serverless experience, not just reading about it. Deliberately not reimplemented in this site’s shared Python `api/`, per this site’s own portfolio-piece isolation convention’s different-runtime trigger.
Database	Azure Cosmos DB (NoSQL API)	Three containers — `techs` (partitioned by `/id`), `jobs` and `coachingHistory` (both partitioned by `/techId`) — the natural query shape throughout is “everything for one tech.”