That's naive without any context to claim. You have to know the source that triggers the code to publish the message, what the message is for, the fault toleran

That's naive without any context to claim. You have to know the source that triggers the code to publish the message, what the message is for, the fault tolerance and availability of the API we're calling before you can even begin to decide. Which you validated perfectly by giving a snarky "what about redundancy" answer to a complicated question.