Using RelStorage 3.0a in production

Brice Vissière <[email protected]> Mon, 30 Sep 2019 00:51:16 -0700 (PDT)
Newsgroups gmane.comp.web.zope.zodb
Message-ID <[email protected]>
------=_Part_879_1624478704.1569829876714
Content-Type: multipart/alternative; 
	boundary="----=_Part_880_1578255328.1569829876714"

------=_Part_880_1578255328.1569829876714
Content-Type: text/plain; charset="UTF-8"

Hi,

We are considering replacing a ZEO/FileStorage instance by a 
RelStorage/postgresql one for our services, in order to solve some 
performance issues. Our tests showed that it's a good call.

But came two questions:

- all the tests were ran with RelStorage 3.0a (a1 to a11), which is still 
under development. If we choose to go with this development version in 
production, I guess we will do it "at our own risks". We are wondering what 
kind of risks? And especially, are there points we should focus on and 
check, in order to minimize those risks?

- our tests were performed with direct connections to postgresql; we should 
also still use a ZEO instance in front of postgresql. We did not try it. Is 
this a good/recommended setup?

Best regard,
Brice

-- 
You received this message because you are subscribed to the Google Groups "zodb" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
To view this discussion on the web visit https://groups.google.com/d/msgid/zodb/83934215-9031-4ccb-8c45-7d3e9227b413%40googlegroups.com.

------=_Part_880_1578255328.1569829876714
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hi,<br><br>We are considering replacing a ZEO/FileStorage =
instance by a RelStorage/postgresql one for our services, in order to solve=
 some performance issues. Our tests showed that it&#39;s a good call.<br><b=
r>But came two questions:<br><br>- all the tests were ran with RelStorage 3=
.0a (a1 to a11), which is still under development. If we choose to go with =
this development version in production, I guess we will do it &quot;at our =
own risks&quot;. We are wondering what kind of risks? And especially, are t=
here points we should focus on and check, in order to minimize those risks?=
<br><br>- our tests were performed with direct connections to postgresql; w=
e should also still use a ZEO instance in front of postgresql. We did not t=
ry it. Is this a good/recommended setup?<br><br>Best regard,<br>Brice<br></=
div>

<p></p>

-- <br />
You received this message because you are subscribed to the Google Groups &=
quot;zodb&quot; group.<br />
To unsubscribe from this group and stop receiving emails from it, send an e=
mail to <a href=3D"mailto:[email protected]">zodb+unsubscri=
[email protected]</a>.<br />
To view this discussion on the web visit <a href=3D"https://groups.google.c=
om/d/msgid/zodb/83934215-9031-4ccb-8c45-7d3e9227b413%40googlegroups.com?utm=
_medium=3Demail&utm_source=3Dfooter">https://groups.google.com/d/msgid/zodb=
/83934215-9031-4ccb-8c45-7d3e9227b413%40googlegroups.com</a>.<br />

------=_Part_880_1578255328.1569829876714--

------=_Part_879_1624478704.1569829876714--