简体   繁体   English

在CRM App数据库中存储电子邮件历史记录的最佳方法是什么

[英]What is the best approach for storing for Email History in CRM App databases

We are building a CRM with a fairly standard database model. 我们正在建立一个具有相当标准的数据库模型的CRM。 Users, Permissions, Contacts, Leads etc. 用户,权限,联系人,潜在客户等

We also want to maintain all email communication, so that it can be stored, searched, and used as business processes backup. 我们还希望维护所有电子邮件通信,以便可以对其进行存储,搜索和用作业务流程备份。

I imagine the amount of email traffic will be quite heavy - leading to a large database really really quick. 我想象电子邮件的流量将非常庞大-导致真正庞大的数据库确实非常快。

Is it safe to bundle this with the CRM app or should it be isolated in its own unique database (probably on its own server). 将其与CRM应用程序捆绑在一起是否安全,还是应该将其隔离在自己的唯一数据库中(可能在自己的服务器上)。

You could use the mysql database as quick lookup for some metadata like date sent, email address, subject or similar as well as a unique id and store everything else related to the mail (like content/attachments) in a nosql database like redis, since you can access those really fast with the unique key. 您可以使用mysql数据库快速查找某些元数据(例如发送日期,电子邮件地址,主题或类似内容)以及唯一ID,并将与邮件相关的所有其他信息(如内容/附件)存储在nosql数据库(如redis)中,因为您可以使用唯一密钥快速访问那些。

we are using this approach to store > 8.000.000 emails and the lookup by email-address and/or date is blazing fast due to indexing. 我们正在使用这种方法来存储> 8.000.000封电子邮件,并且由于建立索引,按电子邮件地址和/或日期进行的查找快速增长。

(if you really need to search the mail content (like fulltext search) I would expect other engines like elasticsearch to be more search speed friendly than mysql fulltext searches) (如果您真的需要搜索邮件内容(例如全文搜索),我希望其他引擎(例如elasticsearch)比mysql全文搜索对搜索速度更加友好)

声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.

 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM