Hi guys,
I am building a web-app that is using a bunch of azure technologies, and includes some integration with quickbooks.
The web app generates messages that are sent to an azure queue. These messages are picked up from the queue and processed by a service running on the same machine as quickbooks. All well and great.
Now, lets say that I am creating a customer in QB (Quickbooks), I would like to return the QB Id to the app's SQL database, so that I can then use this ID when creating invoices against that customer.
So my question is as follows: where should I update the DB with the QB_ID? Specifically, should the service return some sort of message to another queue in azure, which can then be picked up by a web-job on the web-app box, or alternatively, maybe the windows service running on the QB box should update the DB field directly?
Which would work better from an architecture/security/performance perspective?
I am building a web-app that is using a bunch of azure technologies, and includes some integration with quickbooks.
The web app generates messages that are sent to an azure queue. These messages are picked up from the queue and processed by a service running on the same machine as quickbooks. All well and great.
Now, lets say that I am creating a customer in QB (Quickbooks), I would like to return the QB Id to the app's SQL database, so that I can then use this ID when creating invoices against that customer.
So my question is as follows: where should I update the DB with the QB_ID? Specifically, should the service return some sort of message to another queue in azure, which can then be picked up by a web-job on the web-app box, or alternatively, maybe the windows service running on the QB box should update the DB field directly?
Which would work better from an architecture/security/performance perspective?