Why Octopus doesn't use the .NET Service Bus (or polling)

Paul Stovell discusses the communication model of Octopus Deploy, which uses a standard client/server approach where the Tentacle listens for connections from the Octopus server. He addresses a common feature request to reverse this model, allowing Tentacles to initiate connections to the server, which could potentially bypass firewall restrictions. However, Stovell argues against this reversal, noting that it could undermine trust with system administrators by circumventing established firewall rules. He suggests that while there might be valid scenarios for reversing the communication model, such as deploying desktop software or dealing with slow firewall rule changes, these cases are exceptions rather than the norm. Stovell emphasizes that the current architecture aligns with traditional operations tools and maintains simplicity, suggesting that altering it could create distrust in the product. Despite potential scenarios that might benefit from a reversed model, he concludes that the implementation effort and potential trust issues do not make it a high-priority feature.