Azure Functions guides for .NET: isolated worker model, dependency injection, bindings, local development and when serverless is the right choice.
Azure Functions are a good fit for event-driven workloads, and a poor fit for everything forced into them. These articles cover the .NET isolated worker model, dependency injection, bindings and the operational details that matter once a function runs in production.
Azure Static Web Apps is primarily a host for static frontend assets, but it can also deploy a small HTTP API alongside the frontend. That API is implemented as an Azure Functions application and is exposed through the …
Read Blog Post
Hono is often associated with Cloudflare Workers and for good reason. Its small routing model, Web Standard API surface and direct fetch integration make it a natural fit for edge runtimes. That association can obscure a …
Read Blog Post
Gestern wurde von Anthony Chu die Roadmap für Azure Functions mit .NET 5 und .NET 6 vorgestellt. Die wichtigsten Punkte will ich kurz zusammen fassen:
Read Blog Post
Microsoft hat gestern die erste Preview für .NET 6 veröffentlicht, das im November 2021 als stabile Version kommen wird. Anbei die aus meinen Augen wichtigsten Punkte:
Read Blog Post
In most cases, Azure IoT Hub messages should be stored for a longer period of time. In fact, there are several ways to achieve this goal - and there are huge differences in performance and price.
Read Blog PostMediatR MediatR is one of the most popular libraries in the .NET environment and describes itself as “Simple, unambitious mediator implementation in .NET”. In the end, MediatR is a perfect library for in-process message …
Read Blog PostAzure Functions provides a very lean way to execute code serverless. So lean, in fact, that there is no dependency injection by default.
Read Blog Post