If you need a cloud-based service bus or a simple to use queue/topic/routing/pub-sub service, then Azure Service Bus is a very good choice at a reasonable price and performance. Typically on-premise we'd use RabbitMQ because it "just works", but if you're building a "cloud-first" application, then this is the one to go with. It's especially easy to integrate with if you're already embedded in the Microsoft ecosystem.
At the suggestion of the contractor (retailer), who has always entrusted us with the Internet environment, we set up this tower server. The CAL upgrade cost associated with upgrading the file server can be greatly reduced because the StrageServer operating system was given as a line. The operability of remote maintenance was also greatly improved by employing the associated management software (iRMC).
Acting as a basic queuing service it works very well.
One of the best parts is that Azure Service Bus can work over HTTPS which helps in strict firewall situations. There is a performance hit if you choose to use HTTPS.
The routing capabilities are quite good when using topics and subscriptions. You can apply filters using a pseudo-SQL-like language though the correlation filters are quick and easy options.
Costs are very reasonable at low-ish volumes. If you're processing 10's of millions of messages a month... it may be a different story.
The support system that more than makes up for it is the determining factor for the choice.
When a RAID disk or power supply failed, the maintenance service alerted me with a monitoring alarm and replaced it quickly before service was interrupted.
RabbitMQ is simple and awesome... but so is Azure Service Bus. Both accomplish the same thing but in different environments. If you're building a cloud-native application - especially one that is serverless by design - Azure Service Bus is the only real choice in Azure. It works well, it's performance, and it's reasonably priced in the Standard tier. From our testing, RMQ is more performant, but it's hard to compare service-based implementations vs RMQ installed on VMs.
With respect to the backup system, I believe that relocation after the replacement was facilitated.
The best solution to the problem was that thanks to Fujitsu Interstage I created a separate cloud to store the data for each individual PC.
Being able to continue the tasks, without the interruption of service due to a hardware failure that was fixed very efficiently, demonstrates the quality of this company's operations.
