Thank You for Rel Storage 3.

[Christopher Lozinski]

I just read your ZODB blog posting from last year:

https://dev.nextthought.com/blog/2019/11/relstorage-30.html

And your RelStorage blog posting:

https://dev.nextthought.com/blog/2019/11/relstorage-30.html#backwards-incompatible-changes

What you have done is really awesome.  I need shared in memory pickle caches.  And you do all of that magic with parallel commits. WOW!   

  

Taking a high level view.   ZODB gives the user a very simple computational model: persistent Python.  Now we also have very high, parallel performance.  Thank you. 

 Initially it was simple implementation.   First came File Storage, then RelStorage, and now RelStorage 3.  The complexity and performance increase over time, making it harder and harder to understand.   So I signed up to follow RelStorage on GitHub and will be reading more about it regularly.   I would love to know how it all works. As always the best way to understand it, would be to help contribute to the documentation.   I am tempted to edit your two blog postings.  Make them easier for beginners (like myself)  to understand.  May I edit them?  

Warm Regards

Christopher Lozinski

https://PythonLinks.info
tel: +48 32 361 3136
Skype: clozinski

[Jason Madden]

> On Jul 13, 2020, at 06:11, Christopher Lozinski <lozi...@PythonLinks.info> wrote:
>
> I just read your ZODB blog posting from last year:
> https://dev.nextthought.com/blog/2019/11/relstorage-30.html
>
> And your RelStorage blog posting:
> https://dev.nextthought.com/blog/2019/11/relstorage-30.html#backwards-incompatible-changes
>
> What you have done is really awesome. I need shared in memory pickle caches. And you do all of that magic with parallel commits. WOW!
>
> Taking a high level view. ZODB gives the user a very simple computational model: persistent Python. Now we also have very high, parallel performance. Thank you.
> Initially it was simple implementation. First came File Storage, then RelStorage, and now RelStorage 3. The complexity and performance increase over time, making it harder and harder to understand. So I signed up to follow RelStorage on GitHub and will be reading more about it regularly.

Thank you for your interest in RelStorage and ZODB!

> I would love to know how it all works. As always the best way to understand it, would be to help contribute to the documentation. I am tempted to edit your two blog postings. Make them easier for beginners (like myself) to understand. May I edit them?

Thank you for your interest in dev.nextthought.com! While posts on dev.nextthought.com undergo a PR+review cycle before being published, once published, generally only minor changes are allowed, such as grammar and spelling typos and example corrections (with a change history). We also don't currently have a policy allowing guest authors. But of course you're more than welcome to link to posts from your own content! And we occasionally tweet or post links on the blog about exciting technical content we discover.

Thanks again,
Jason