Oh, the Azure Service Bus emulator issue was closed in the last year, and there is now a way to run a limited version of Azure Service Bus locally. I am glad that they overcame the initial hostility toward users by Sean Feldman, which is an example of how not to engage with your user base.

I gave it a try today, and spinning it up seemed fairly straightforward and the documentation is surprisingly okay. The config.json is not understandable to me as a front-end developer trying to get it to work.

However the back end developers that make the API that I rely on for this client use MassTransit and ServicesBusAdministrationClient so I am still out of luck until those issues get prioritized.

I think there’s also an issue with using an existing database after restarting the container, but I’ll worry about that when I can actually use the emulator.

Local development story? · Issue #223 · Azure/azure-service-bus

Trying to get an understanding of what the local development story is. RabbitMQ for example can be installed on a dev machine, or run as a Docker container. If I have development/build images that ...

GitHub
Nebraska.Code 2025 hosted on Whova

July 23 – 25, 2025, Lincoln, NE

Still no solution to this #azure #azureservicebus problem https://github.com/Azure/azure-sdk-for-net/issues/40773. As the SDK team refers to the Azure community feedback forum, here it is … https://feedback.azure.com/d365community/idea/0c0522b6-5a9e-ee11-a81c-000d3a05396f
[BUG] Paging through a considerable amount of queues in a namespace results in inconsistent page and total item count results · Issue #40773 · Azure/azure-sdk-for-net

Library name and version Azure.Messaging.ServiceBus, Version=7.17.1.0 Describe the bug I have a small service bus browser tool https://github.com/sergevm/azure-servicebus-browser that has some sear...

GitHub

@CodeAndCoffee Building out the feature wish-list for the game I'm thinking of building, then working on some POCs and subjecting them to load-testing to make sure my assumptions are correct about the tech stack and approach I want to use.

#dotnet #azure #azurefunctions #azureservicebus #gamedev

I'd like to create an event based, ledger type system.

My 1st thoughts are:

#DAPR and #AzureServiceBus

I need a pub/sub architecture but also a 'ledger' style, accounting-based system to track state.

Thoughts?

#designpatterns

GitHub - damienbod/AspNetCoreServiceBus: ASP.NET Core with Azure Service Bus

ASP.NET Core with Azure Service Bus. Contribute to damienbod/AspNetCoreServiceBus development by creating an account on GitHub.

GitHub
@nova I wrote a Charging Station Management System based on the Open Charging Point Protocol v1.6/2.0.1. It's written in #dotnet6 and hosted in #azure. I use #azureservicebus for communication between the different services. Frontend is a plain old #angular SPA. My wallbox connects via #websockets and sends and receives all kind of data to monitor and manage charging sessions. I mainly used it as a learning project to explore #dddesign a little further.

Do you need a #azure service bus explorer app for Mac? (The app is of course developed with .NET MAUI)

https://apps.apple.com/se/app/azservicebus/id6444410679?l=en&mt=12

#macapp #azureservicebus #servicebus #dotnet #dotnetmaui

Another way to say the above is this:

`Logs, with apppropriate notifications, are a perfectly valid Deadletter infrastructure for messages that cannot reasonably be reprocessed automatically.`

#EventDriven #Microservices #ApacheKafka #AzureServiceBus

Deadletter queues or topics are only required in 2 cases:

1. When the message can be automatically processed in the future
2. When infrastructure constraints make them the simplest option

If a message cannot be automatically processed in the future (ie order needs to be maintained) it is better to log the failed message with appropriate notifications rather than putting it into deadletter infrastructure such as a queue.

#EventDriven #Microservices #ApacheKafka #AzureServiceBus