On Sun, 2009-11-15 at 00:31 -0700, Shane Hathaway wrote:
Roché Compaan wrote:
On Sat, 2009-11-14 at 14:23 -0700, Shane Hathaway wrote:
I think proper construction of horizontally scalable databases must be
done partly at application level, since a lot of the issues to be solved
are
On 11/13/09 21:33 , Shane Hathaway wrote:
I've been studying how to build an enormous database based on what I
know. There are an incredible number of distributed databases these
days, but all of them concern me in one way or another.
Can you share some of those concerns with us? I'ld be
Roché Compaan wrote:
On Fri, 2009-11-13 at 13:33 -0700, Shane Hathaway wrote:
Stephan Richter wrote:
http://svn.zope.org/z3c.sharding/trunk
Great stuff! This approaches scaling a large data set at application
level though. Don't you think a ZODB storage doing this for you would
solve the
Wichert Akkerman wrote:
On 11/13/09 21:33 , Shane Hathaway wrote:
I've been studying how to build an enormous database based on what I
know. There are an incredible number of distributed databases these
days, but all of them concern me in one way or another.
Can you share some of those
On Sat, 2009-11-14 at 14:23 -0700, Shane Hathaway wrote:
Roché Compaan wrote:
On Fri, 2009-11-13 at 13:33 -0700, Shane Hathaway wrote:
Stephan Richter wrote:
http://svn.zope.org/z3c.sharding/trunk
Great stuff! This approaches scaling a large data set at application
level though.
Roché Compaan wrote:
On Sat, 2009-11-14 at 14:23 -0700, Shane Hathaway wrote:
I think proper construction of horizontally scalable databases must be
done partly at application level, since a lot of the issues to be solved
are specific to the application.
What are the issues you're talking
Am 14.11.09 23:33, schrieb Shane Hathaway:
I think that by very critical, the MongoDB authors are referring to
applications that must not allow conflicting updates. Conflict
resolution is probably my main concern with all of these new databases.
I have no doubts about ZODB's
Hello,
I think we can look at this at 2 levels.
1.: As your app uses ZODB. Then this is your app's
problem/reponsibility. You use a nosql contender directly from
your app and it's your responsibility to deal with it.
2.: On the ZODB Storage level. So far I can see that level needs
On Fri, 2009-11-13 at 10:58 +0100, Christian Theune wrote:
On 11/13/2009 10:42 AM, Adam GROSZER wrote:
Hello,
I think we can look at this at 2 levels.
1.: As your app uses ZODB. Then this is your app's
problem/reponsibility. You use a nosql contender directly from
your app
On Friday 13 November 2009, Roché Compaan wrote:
We had such an opportunity about 2 years ago and although the client
never reached (and probably will never) reach the membership they
dreamed about, they did pay us to develop a storage for members that
could scale to more than a 100 million
Stephan Richter wrote:
On Friday 13 November 2009, Roché Compaan wrote:
We had such an opportunity about 2 years ago and although the client
never reached (and probably will never) reach the membership they
dreamed about, they did pay us to develop a storage for members that
could scale to
I am very intrigued now to setup an EC2 cluster and install a z3c.sharding
based solution demonstrating 100M users with some data. Mmmh...
That is the great thing about EC2. You can do massive experiments on the cheap.
Actually one of our interns is doing some work on ZODB. He is doing
On Fri, 2009-11-13 at 13:33 -0700, Shane Hathaway wrote:
Stephan Richter wrote:
On Friday 13 November 2009, Roché Compaan wrote:
We had such an opportunity about 2 years ago and although the client
never reached (and probably will never) reach the membership they
dreamed about, they did
Hello,
Is there someone in the ZODB development team following this:
http://www.rackspacecloud.com/blog/2009/11/09/nosql-ecosystem/
Regards,
--
Encolpe DEGOUTE
http://encolpe.degoute.free.fr/
Logiciels libres, hockey sur glace et autres activités cérébrales
Encolpe Degoute wrote:
Is there someone in the ZODB development team following this:
http://www.rackspacecloud.com/blog/2009/11/09/nosql-ecosystem/
It is possible that ZODB unfortunately occupies the same space as SQL in
the CAP triangle:
http://camelcase.blogspot.com/2007/08/cap-theorem.html
15 matches
Mail list logo
