sfeldman.NET
.NET, code, personal thoughts
-
Event Grid advanced filters and value pooling
-
Deploying an Azure WebJob with GitHub Actions
-
Azure Service Bus SDK - Safe Batching
-
Service Bus Explorer in Azure Portal
-
Azure Service Bus SDK - Receiving ServiceBusReceivedMessage(s)
-
Azure Service Bus SDK - Sending ServiceBusMessage(s)
-
Azure Service Bus SDK - ServiceBusClient
-
The future of Azure Service Bus .NET SDK
The Azure Service Bus SDK for .NET is one of the oldest Azure SDKs. Its first public appearance as a NuGet package
WindowsAzure.ServiceBus
goes back to 2011. Back then, it was for .NET Framework and closed source. The package had an excellent mileage and is still used on multiple projects even today. And then the .NET Core and Standard have landed. Times have changed, open-source has become much more mainstream and accepted. The Azure Service Bus .NET SDK has moved into the brand new world with a successor package,Microsoft.Azure.ServiceBus
. Started in early 2017, it showed up, causing some havoc to the brownfield projects. These projects were forced to face a complete rewrite due to the nature of the disruptive changes introduced by the new package. Once the dust has settled, the old and the new SDK nomenclature has established, and slowly projects have embraced the new SDK. There was a balance in the Force. -
Announcing Azure Events Wishlist
Azure Event Grid is by far not a new kid on the block. Announced in January 2018, the service promised to get us closer to the event-driven architecture and replace the cumbersome polling for communication between services with a simple mechanism - pub/sub. Other the course of two years, we've seen some Azure services adding a few events, unleashing the power of Event Grid. Yet the list of services and their corresponding events are still shy to call it done-done. Current services providing some events are:
-
Understanding Azure Service Bus Prefetch
Working with a remote broker can be a challenge at times. The latency caused by the roundtrip to the broker to fetch a single message can exceed the processing time of that message. To help with this problem, Azure Service Bus (ASB) offers a prefetching option to retrieve messages before they are requested. This option is available with all three clients capable of retrieving messages:
MessageReceiver
,QueueClient
, andSubscriptionClient
. When a message is requested, and this option is turned on, the ASB client retrieves more messages. The additional messages are kept in a memory buffer until the user code requests the next message. Except for this time, the client will not fetch it from the broker but rather from the in-memory buffer. That beats the latency and improves the overall throughput of the application or the system performing message processing.