Re: ZODB storage for cassandra

Thanks a lot for response.

Databases like Cassandra are non-transactional. Among these databases, 
Cassandra provides a weaker level of consistency. See 
https://wiki.apache.org/cassandra/ArchitectureOverview.

ZODB is transactional and any storage implementation needs to maintain 
transactional semantics.

I am largely aware of these facts.

NoSQL databases like Cassandra are very good for collecting raw data which 
occurs as a result of discrete events and is never modified (because then 
it wouldn't be raw).  For this kind of data, there is no need for 
consistency between different data. All that matters is durability.  This 
is an important application and it is, IMO, a mistake to use a 
transactional database for this application (unless you're actually 
collecting so little data that write scalability doesn't matter).

I fully understand the point raised here, but I have a problem. I have an 
existing zope application(lots of browser, SOAP, xmlrpc views) which my 
employer does not want to rewrite. In this application we need massive 
scaling at database writing. We can give back seat to consistency or can 
handle consistency at application level. Can you suggest any alternate 
solution ? 



On Monday, 15 May 2017 16:37:42 UTC+5:30, Jim Fulton wrote:
>
>
>
> On Mon, May 15, 2017 at 1:43 AM, Sanjay Rao <[email protected] 
> <javascript:>> wrote:
>
>> Hi,
>>
>> Is there any ZODB storage available for Cassandra ?
>>
>
> No, and I hope there never is.
>
> Cassandra provides linear scaling for writes.
>>
>
> Writing to /dev/null is even faster and scales very well horizontally.
>
> Databases like Cassandra are non-transactional. Among these databases, 
> Cassandra provides a weaker level of consistency. See 
> https://wiki.apache.org/cassandra/ArchitectureOverview.
>
> ZODB is transactional and any storage implementation needs to maintain 
> transactional semantics.
>
> NoSQL databases like Cassandra are very good for collecting raw data which 
> occurs as a result of discrete events and is never modified (because then 
> it wouldn't be raw).  For this kind of data, there is no need for 
> consistency between different data. All that matters is durability.  This 
> is an important application and it is, IMO, a mistake to use a 
> transactional database for this application (unless you're actually 
> collecting so little data that write scalability doesn't matter).
>
> Jim
>
> -- 
> Jim Fulton
> http://jimfulton.info
>

-- 
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].
For more options, visit https://groups.google.com/d/optout.