We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
你好,我最近也想开发一个类似的消息系统,关于回调失败这个地方我有以下疑问,想与您讨论一下 如果在服务运行正常及配置参数填写正确的情况下,为何会出现回调失败的情况? 如果配置参数填写错误,回调失败后重试也是失败,那这样重试的意义在哪?
The text was updated successfully, but these errors were encountered:
应该假设调用的第三方系统可用性没有100%,理论上也做不到100%可用性,所以需要重试策略保证。参数错误你测试就过不了不在这个讨论范畴
Sorry, something went wrong.
感谢回复🙏,在考虑问题初期确实没有把第三方系统考虑进去。 如果消息及发送等数据保存在消息通知服务中,第三方系统只调用接口来查询消息或操作消息。这样省略了第三方系统集成时的建库操作。集成接入简单的同时,保证自身服务可用就可以了,不用考虑回调失败的问题。 这种方案是否可行?
No branches or pull requests
你好,我最近也想开发一个类似的消息系统,关于回调失败这个地方我有以下疑问,想与您讨论一下
如果在服务运行正常及配置参数填写正确的情况下,为何会出现回调失败的情况?
如果配置参数填写错误,回调失败后重试也是失败,那这样重试的意义在哪?
The text was updated successfully, but these errors were encountered: