短信网关可能存在的问题?
短信网关可能出现哪些问题?
如果您正在尝试创建一个具有大量交易的系统? 数据丢失现象猖獗吗?短信网关有什么问题吗?或者有一个关于问题的巨大问题?
What could be the possible problems of an sms gateway?
If you are trying to create a system having large volume of transactions?
Is data loss rampant? are there any issues about SMS gateway? or there a huge issue about the problems?
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论
评论(2)
我还注意到这篇文章很旧,但希望这会有所帮助。
因为您没有提到如何发送消息,即通过 GSM sim,或通过聚合器。我猜你在谈论数据库存储?
我们这样做的方法是将所有消息存储在 mysql 表 tbl_sms_queue 中,例如,它被分配给一个活动,并且还有一个状态片段 ENUM(待处理或已发送)。
表示例:
然后我们的 gearman 服务器解析数据库,我们每分钟可以发送大约 4500 - 5000 条消息。
仅供参考:我是一个批量短信平台的架构师,我们的数据库后端是集群 mysql 和 gearman 含义的自定义安装。
I also notice this post is old but hope this helps.
As you haven't mentioned how you are sending the messages i.e. VIA GSM sim, or through a aggregator. I am guessing you are talking about database storage?
The way we do it is store all the messages in a mysql table tbl_sms_queue for instance, this is assigned to an campaign and also has a status frag ENUM(pending or sent).
table sample:
Then our gearman servers parse through the db, we can sent approx 4500 - 5000 messages per minute.
FYI: I am an architect of an bulk sms platform and our database backend is a custom installation of clustered mysql and a gearman implication.
我不认为“数据丢失”是一个问题。我认为您可能遇到的问题是发送者/接收者一次只能处理 1 条消息。
发送/接收短信需要 X 秒,如果您确实发送/接收大量此类短信,您的队列将迅速增长,您很快将需要能够使用更多电话线路一次发送/接收多条短信。
I don't think "data loss" is a concern. I think the problem you can encounter is that the sender/receiver can only work with 1 message at once.
Sending/receiving a SMS take X seconds, and if you indeed send/receive a lot of these short messages, your queue will grow rapidly and you will soon need to be able to send/receive multiple SMS at once, using more phone lines.