跟踪电子邮件的最佳方式 - UUID 与 ID 号
需要跟踪我们组织内的 100 万个电子邮件地址以进行营销和客户响应。已决定自行开发。
对其他人正在做的事情做了一些研究后，我注意到似乎所有人都使用 uuid（guid）进行跟踪。这是跟踪电子邮件活动的最佳方式吗？
在我们开始破解之前还有其他建议吗？
need to track 1 million email addresses within our organisation for marketing and customer response. It has been decided to develop in-house.
having done a little research into what others are doing I have noticed that all seem to use uuid (guid) for tracking. Is this the best way to track email activity?
Any other advice before we get cracking?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
UUID的优点是它们可以由多台机器独立生成，并且不会发生冲突。使用 ID 号时，您需要某种方法来确保生成的 id 不会发生冲突。如果您在一台机器上执行此操作，则可能很简单。如果你想分发这个作品，那么你可能需要多考虑一下。 ID 的优点是它们可以是数字，因此可以更小地存储在数据库中，并且还可以暗示某种顺序。暗示使用 GUID 进行排序会更加困难 (虽然并非不可能）
如果是我，我只会使用 GUID，从长远来看可能会更简单。
UUID has the advantage that they can be generated by many machines independent of each other and they will not clash. Using an ID number you need some way to make sure that the ids generated do not clash. If you are doing this on a single machine, it may be simple. If you wish to distribute this work, then you may need to think a little more about it. ID's have the advantage that they can be numeric and so are smaller to store in the DB, and can also imply some ordering. Implying ordering is more difficult with GUIDs (although not impossible)
If it was me, I'd just go with a GUID, it'll probably be simpler in the long run.