Hi
We are investigating to see if mailpiler is a suitable replacement for MailArchiva. A few weeks ago I made a feature request to extend piler's authentication to generic ldap, and this feature was released in 2 days. This great responsiveness on your part was very well received, and the generic ldap authentication is working quite well. However, because mail ingestion and client churn generate a lot of activity in ISP scale environments, a single server installation would incur heavy database and disk activity when provisioning and purging data for new and cancelled clients. What is the recommended architecture to scale piler up to "20 000 users and beyond"?
How would you architect Mailpiler to provide highly scalable capacity, performance and availability? Bearing in mind the possible impact of ingestion and data purging on both the file system and the database. Do you have any examples or case studies on clients from large enterprises who have moved to mailpiler, and how did they meet the architectural requirements?
Regards
Darryl Sutherland
|
Darryl Sutherland Senior Linux Administrator |
|||||||||
 |
|
||||||||
PS: Download our free whitepaper on email archiving best practices here!
Support: +27 (0)11 262 3628 | +27 (0)861 0 SYNAQ
Block D, Sandhavon Office Park, Pongola Crescent, Eastgate Ext. 4, Sandton
