Use getQueueUrl API to generate sqsUrl using sqsName and awsAccountId or simply hardcode the sqsUrl string. What is the recommendation?

There are two ways to get the sqsUrl:

A. We can simply hardcode the static url string in the code.

Pros:

a. No API call, hence less latency.

b. Simple to write and less line of code. Will have to define just the sqsUrl for each sqs in Configuration.

c. Many services in Amazon use this only, probably to save latency.

Cons:

a. If AWS changes the url structure in future, then the code will break. And we have to go change the url in code. But slim chance of happening this. They will make sure of compatibility.

b. Kind of hardcoding, not a good coding practice. (My opinion)

B. Other way is to programatically create the sqsUrl using getQueueUrl api, which accepts sqsName and awsAccountId (optional, only required if sqs’s account is different than caller’s account.)

Pros:

a. If we want to send the message to some random team’s sqs, but they didn’t provide the sqsUrl. They just provided the name of sqs and account id. In that case, generating url programatically can help.

b. If AWS changes the url structure in future, the code will require no changes, and things will work as it is.

c.There must be some reason why SQS provided getQueueUrl api, to avoid directly using url/arn. (Yet to find any documentation where AWS recommends using this. )

Cons:

a. Extra dependency on an api getQueueUrl, extra latency of ~200 ms. But should not be a concern when this much latency doesn’t matter. For ex: Offline systems, Postprocessing scenario, etc.

b. Less lines of codes.