I am trying to figure out whether or not archiveopteryx is the right solution for a large scale (say millions of users) mail. There is not much on this topic (or user experiences) on google so I am reaching out to you on this list.
This would be mostly a webmail system, so I figured using DB directly would be more efficient/easy. I have experience with scaling mysql and I assume postgresql would be similar conceptually. My initial thought is to shard by putting proxy (nginx) in-front. Ideally I would also like to store attachments on disk (not sql tables [blob], accessible by web heads [with auth]) and store only the path in DB. This would work fine for webmail, but not for typical mail (imap/pop) client - a compromise I am willing to take. I have zero to little experience with coding in C++ but I am willing to take a stab. I am also wondering if there is any new roadmap or a group of individuals who are currently working expanding archiveopteryx's features. Please share if any one has had any experiences with running a farm of archiveopteryx servers & also if there are any limitations that I am not aware off. Thanks
