[horde] Guidance on SQL vs. NoSQL storage

[Nels Lindquist]

On 2021/03/13 8:47 a.m., Michael J Rubinsky wrote:
> 
> Quoting Ralf Lang <lang at b1-systems.de>:
> 
>> Am 12.03.21 um 23:17 schrieb Nels Lindquist:
>>>
>>> We recently added a node to our Horde access server, and I figured I'd
>>> take the opportunity to try out MongoDB as a NoSQL storage method for
>>> shared data across the cluster.
>>>
>>> Unfortunately it hugely spiked the load on the server, and I ended up
>>> backing out the config and reverting to PostgreSQL for the shared
>>> storage.
>>>
>>> Is there any guidance or recommendations for the kinds of data it
>>> might be appropriate to consider using one over the other? eg.
>>> ActiveSync caching vs. IMAP caching vs. session data, preferences, etc.?

<snip>

>> I want to reduce DB writes for data I don't really care about / can
>> afford to be lost on crashes. On the other hand, any memory spent on a
>> DHT is memory you could also spend on SQL database caches. Any tangible
>> benefit comes only with scale.

<snip>

> In reference to ActiveSync usage, I can tell you that the only reason I 
> wrote the Mongo driver is that a client wanted it. At the time it was 
> because ActiveSync was the only part of his installation that still 
> needed a SQL database. I can also tell you in an unscientific manner 
> that I have found the performance to be fairly lacking and I wouldn't 
> recommend it unless you have a very specific need for it.

Thanks to all who replied; just to finish the conversation for any 
future list searchers, I threw more RAM at the PostgreSQL cache and 
increased connection limits; everything is working nicely without any 
NoSQL in the equation.

Nels Lindquist
----
nlindq at maei.ca