<@U7VH2756H>at first glance the only tricky thing ...
# suitescript
s
@T_GDBat first glance the only tricky thing using Azure service bus may be negotiating authentication https://docs.microsoft.com/en-us/azure/service-bus-messaging/service-bus-sas
t
Hey @stalbert thanks. And if I would like to POST Messages from topics in the Service Bus to RESTlets in Netsuite, do I need to create a .NET App in between to 'subscribe' and 'listen' to the new messages from the topics ? Or is it possible to do it directly from NetSuite?
s
again the challenge going directly to a RESTlet would be authentication on the NS side.
I am not sure it's possible, but I'd presume rather than creating a .NET app I'd recommend an Azure Function to do that work if possible
at least that way you could use the same language across your NetSuite and ServiceBus adapter and avoid building a more complex standalone .NET app.
My assumption is that Azure functions has some way to subscribe to a Service Bus topic.
t
Thanks I'll get a look at the Azure Functions, I didn't know them. It looks way easier indeed. thanks
s
definitely easier than building, hosting and caring for an entirely separate .NET app. Indeed, avoiding such an app is a motivation for using a cloud based service bus in the first place 🙂 If you built a .NET app, IT could be the service bus/queue itself.
t
Yes definitely easier 🙂 So from Azure with the Azure Functions you think I'll be able to 1) Subscribe to the topics and get the messages from the Bus (ServiceBusTopicTrigger ) 2) Send and Get requests to/from Restlets in Netsuite (with HTTPTrigger) 3) Send messages back to the ServiceBus. ? That would be perfect
s
Yes, that looks feasible