General discussion on installation and configuration of SOGo

Text archives Help

Re: [SOGo] SOGo Scalability Approaches, Ideas ?

Chronological Thread 
  • From: tarjei < >
  • To:
  • Subject: Re: [SOGo] SOGo Scalability Approaches, Ideas ?
  • Date: Mon, 29 Nov 2010 08:15:32 +0100
  • Openpgp: id=74AFCDF2

Hash: SHA1

Hi Thre,
On 11/29/2010 07:32 AM, Mohit Chawla wrote:
> Hi,
> I'd like to know how folks around here are actually scaling SOGo
> deployments. Not trade secrets, but at what levels does scalability
> needs to be taken care of.
> So, if I have say, two SOGo servers, then what would be the correct way
> for preserving sessions across those nodes ?
Are you sure you need to? I'm not sure, but if SOGo follows the REST
principles then you might not have to.
> To be more specific, consider a round-robin dns deployment in place for
> these nodes, with TTL ~30 seconds. Then in case of a node failure, what
> all data and session stores need to be taken care of ? Does it make
> more sense to have a single sql database (on a SAN maybe) or
> multi-master replication across the nodes ?
How big is your deployment? Have you considered separating the DB from
the frontend nodes?

> What about memcached ? Does it need to be replicated as well ? At what
> other levels do I need to be concerned ?
Replicating memcached is a good idea if you got many hits across the
servers - or if sessions needs to be replicated.

Other approaches to consider:
- - look into using varnish[1] to speed up repeated requests.
- - if you got massive scale issues, consider sharding your users into
separate boxes.
- - consider using ningx for loadbalancing instead of DNS.


- --
Tarjei Huse
Mobil: 920 63 413
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla -


Archive powered by MHonArc 2.6.16.

Top of page