Hi,
For IMAP (your a), there has been some progress, but the points
mentionned in the thread you reference are still applicable: still many
technical challenges and not time line.
For mailbox (your b), we have an HBase implementation only usable via
POP3/SMTP (your c) in a distributed env (if you want to use it via IMAP,
you fall in the technical requirements mentionned previously).
The spool (your e) is based on activemq, so it can be distributed with
an HA. This has been talked from time to time on this mailing list, but
nobody reported to have used it untill now.
Hope this helps,
Eric
On 29/11/2012 04:31, Raymond Sellars wrote:
Hi
Does James v3 provide for any high availability (load balanced and fail
over) deployment yet.
I'm interested in
a) deploying multiple James servers behind a load balancer to give load
balanced and failover for IMAP clients.
b) what kind of clustered storage setup (GFS vs NFS vs Database)
requirements are need or if the application logic handles multiple servers
b) multiple James servers for inbound SMTP traffic. Again behind a load
balance although I understand MX records can be used in part for this.
Looking of active active server processing for through put
c) fail over persistency of the spool?
Closest reference I can find is a question back in 2011 suggesting it's
not available yet yet:
http://www.mail-archive.com/[email protected]/msg12755.html. Is
this still accurate
Thanks
Raymond
-----------------
Raymond Sellars
Solution Architect . Orion Health
www.orionhealth.com <http://www.orionhealth.com/>
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
