Re: Using RelStorage 3.0a in production

------=_Part_6480_352172375.1571183295441
Content-Type: multipart/alternative; 
	boundary="----=_Part_6481_445666997.1571183295441"

------=_Part_6481_445666997.1571183295441
Content-Type: text/plain; charset="UTF-8"


On Monday, 30 September 2019 21:39:17 UTC+10, Jason Madden wrote:
>
>
> We are also using RelStorage 3.0 in what I think is a fairly large 
> production setting (for example, one large single database is around 100GB 
> and 33 million objects; there are currently about 180 client connections to 
> it).


Out of interest is this a Zope app or something else? We are working 
through a prototype of a non-Zope app (Pyramid + ZODB) and coming from the 
usual SQL background we get tripped up on how to work through data 
structures and indexing etc. In an application like this what would you 
use? We are currently working with repoze.catalog for search requirements 
and seems to be working well but we have a feeling in the back of our minds 
that we are potentially missing the best options. Given that ZODB doesn't 
really need much documentation to get going, what is documented is great 
for the the basics, however something along the lines of a cookbook for how 
to model data and provide search/indexing etc would be nice.

Any thoughts on this are much appreciated - the reduction in code, layers 
of abstraction and performance improvements with ZODB over SQL/ORM are very 
appealling.

Regards,
Peter Wilkinson

-- 
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/3f45bfc0-f977-46b4-be73-cab8d904f152%40googlegroups.com.

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

<div dir=3D"ltr"><br>On Monday, 30 September 2019 21:39:17 UTC+10, Jason Ma=
dden  wrote:<blockquote class=3D"gmail_quote" style=3D"margin: 0;margin-lef=
t: 0.8ex;border-left: 1px #ccc solid;padding-left: 1ex;">
<br>We are also using RelStorage 3.0 in what I think is a fairly large prod=
uction setting (for example, one large single database is around 100GB and =
33 million objects; there are currently about 180 client connections to it)=
.</blockquote><div><br></div><div>Out of interest is this a Zope app or som=
ething else? We are working through a prototype of a non-Zope app (Pyramid =
+ ZODB) and coming from the usual SQL background we get tripped up on how t=
o work through data structures and indexing etc. In an application like thi=
s what would you use? We are currently working with repoze.catalog for sear=
ch requirements and seems to be working well but we have a feeling in the b=
ack of our minds that we are potentially missing the best options. Given th=
at ZODB doesn&#39;t really need much documentation to get going, what is do=
cumented is great for the the basics, however something along the lines of =
a cookbook for how to model data and provide search/indexing etc would be n=
ice.</div><div><br></div><div>Any thoughts on this are much appreciated - t=
he reduction in code, layers of abstraction and performance improvements wi=
th ZODB over SQL/ORM are very appealling.</div><div><br></div><div>Regards,=
</div><div>Peter Wilkinson</div></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/3f45bfc0-f977-46b4-be73-cab8d904f152%40googlegroups.com?utm=
_medium=3Demail&utm_source=3Dfooter">https://groups.google.com/d/msgid/zodb=
/3f45bfc0-f977-46b4-be73-cab8d904f152%40googlegroups.com</a>.<br />

------=_Part_6481_445666997.1571183295441--

------=_Part_6480_352172375.1571183295441--