Building Event-Driven Architectures with Azure Event Grid and Functions
Event-driven architecture requires careful design but delivers superior scalability and resilience for distributed systems.
9 articles
Event-driven architecture requires careful design but delivers superior scalability and resilience for distributed systems.
Applying CQS (Command Query Separation) in Azure Functions is a pattern I've found genuinely useful for keeping serverless code maintainable as the number…
Create a new Function App with Node.js 18: Update your configuration: Azure Functions v4 introduces a new programming model: Use the built in fetch without…
Functions has supported "any language" via the worker model for a while, but custom handlers are the cleaner option when your runtime isn't on the supported…
The first Azure Function project I shipped used static everything. Static config, static SQL helpers, static logger. It worked—until I tried to write a unit…
Cold starts on Consumption plan kill credibility. I've watched a perfectly good HTTP-triggered function get blamed for "the API being slow" because the…
Static Web Apps with the integrated Functions backend is the deployment story I keep recommending for small SaaS dashboards and internal tools. Static…
Bindings let you focus on business logic, not plumbing.
Function chaining, fan-out/fan-in, human interaction, and eternal orchestrations — Durable Functions exposes a small set of patterns that cover most…