sfeldman.NET

Last week at the Calgary .NET usergroup presentation on Azure Service Bus I was talking about different options the services provides. Along with that, have also noted the quotas and limits subject to tier and usage. There were good questions asked, and one of those question I'd like to highlight here - choosing what topology to use with Azure Service Bus.

Azure Service Bus will not accept a transaction with more than a 100 messages. Not even if you send a batch. It is still a subject to the maximum 100 messages. If you try to send more, the exception "Cannot send more than 100 messages in a single transaction." will be upon you.

When it comes to receiving messages with ASB, there are plenty of options:

Processing with Azure EventHubs can be significantly simplified if using EventProcessorHost. EventProcessorHost is using Azure Storage account to track last read locations (pointers) in event hub partitions.

Last week GitHub has introduced what seems like a small feature, but a huge comments de-clutter if you ask me: reactions. I've been using Slack for quite a while and among the feature that slack has had for a while was reactions for comments. From the UI perspective, reactions allow to provide the needed feedback w/o taking too much of the vertical space.

Azure Service Bus has a rich pub/sub mechanism supporting multiple options.

Tooling is an important part of the development experience. No matter how good a service you're using is, if there are no decent tools, you always have that disgruntled feeling about the entire experience. When developing against hosted services, tools are either coming from the service provider or a third party.

Null-Conditional Operator in C# 6 (?.), also known as "Elvis" operator, has allowed compacting code by removing boilerplate code for a null check to avoid NullReferenceException. But there's more to that than just a null check. I've run into a case where Elvis operator also removed need for an extra code to implement a Decorator pattern, which resulted in removing complexity. Here's the original code implemented using Decorator pattern: