Functioneel beheerder integraties

GitHub - temporalio/temporal: Temporal service

Temporal service. Contribute to temporalio/temporal development by creating an account on GitHub.

Developing Azure Functions with Aspire and the Service Bus Emulator

A quick guide on how to setup the Azure Service Bus emulator and a Azure Functions queue trigger using .NET Aspire

Using Azure Service Bus Queues with ASP.NET Core Services

This article shows how to implement two ASP.NET Core API applications to communicate with each other using Azure Service Bus. The ASP.NET Core APIs are implemented with Swagger support and uses an …

Azure Service Bus PowerShell Module

I recently worked with Azure Service Bus again. Service Bus was the messaging system of the microservice we were building for a customer. As part of that design we needed to test the performance of our application and we needed to make this simple, and flexible.Azure Service Bus PowerShell ModuleOur tests consisted of adding and removing messages onto Azure Service Bus Topics, many of them. It was okay for those messages to be all identical.Unfortunately, the Az.ServiceBus PowerShell module does not contain any cmdlets to send a message to a topic, and also none to “delete” them. So I got to work and developed my own module. Tl;Dr find the module hereFor now, the module consists of only two public cmdlets: Send-SbTestMessage Send a message once or many times over and over to your Service Bus Topic Receive-SbMessage Receive a single message or many messages. The received message will also be “deleted” from the Topic. AuthenticationThis module depends on an authenticated user session that has access to the Service Bus, depending on the cmdlet used the Azure Service Bus Data Receiver or Azure Service Bus Data Sender role is required.Special case: Azure Cloud ShellWhenever I can I recommend people use Cloud Shell to interact with their Azure cloud. For this module though there is a requirement for a user to be able to get an Azure Bearer token for a specific API endpoint. This usually works well locally, but because Cloud Shell by default uses MSI (Managed System Identity) to authenticate to Azure there is an extra step required for this module to work.Connect-AzAccount -DeviceCodeThis will ensure one is properly logged in to a session and won’t get the following error message:ManagedIdentityCredential authentication failed: Service request failed.Status: 400 (Bad Request)InstallationThe module is easily installed from the PowerShell Gallery using the following simple one-liner:Install-Module -Name AzureServiceBusManagement -Scope CurrentUserPowerShell RunspacesI attempted to develop the module with performance in mind. PowerShell Runspaces are being used to parallelise the sending or retrieving of messages. Service Bus itself should be absolutely fine with the amount of messages per second one sends or requests from it, so I felt this was good design.Feedback / ContributionFeel free to leave feedback here, on the GitHub repo itself or get in touch with me on Twitter.