Prev: uw-p and make-thread
Next: Hi for those who loves fashion.. check this out :)
From: Xah Lee on 9 Mar 2010 09:24
On Mar 8, 11:14 am, Duncan Booth <duncan.bo...(a)invalid.invalid> wrote:
> Xah Lee <xah...(a)gmail.com> wrote:
> > For example, consider, if you are within world's top 100th user of
> > database in terms of database size, such as Google, then it may be
> > that the off-the-shelf tools may be limiting. But how many users
> > really have such massive size of data?
>
> You've totally missed the point. It isn't the size of the data you have
> today that matters, it's the size of data you could have in several years'
> time.

so, you saying, in several years, we'd all become the world's top 100
database users in terms of size, like Google?

Xah
∑ http://xahlee.org/

☄
From: Duncan Booth on 10 Mar 2010 12:26
Xah Lee <xahlee(a)gmail.com> wrote:

> On Mar 8, 11:14 am, Duncan Booth <duncan.bo...(a)invalid.invalid>
> wrote:
>> Xah Lee <xah...(a)gmail.com> wrote:
>> > For example, consider, if you are within world's top 100th user of
>> > database in terms of database size, such as Google, then it may be
>> > that the off-the-shelf tools may be limiting. But how many users
>> > really have such massive size of data?
>>
>> You've totally missed the point. It isn't the size of the data you
>> have today that matters, it's the size of data you could have in
>> several years
> '
>> time.
>
> so, you saying, in several years, we'd all become the world's top 100
> database users in terms of size, like Google?
>
No, I'm saying that if you plan to build a business that could grow you
should be clear up front how you plan to handle the growth. It's too late
if you suddenly discover your platform isn't scalable just when you need to
scale it.

From: Xah Lee on 10 Mar 2010 17:36
On Mar 10, 9:26 am, Duncan Booth <duncan.bo...(a)invalid.invalid> wrote:
> No, I'm saying that if you plan to build a business that could grow you
> should be clear up front how you plan to handle the growth. It's too late
> if you suddenly discover your platform isn't scalable just when you need to
> scale it.

Right, but that doesn't seems to have any relevance about my point.
Many says that scalability is key to NoSQL, i pointed out that unless
you are like google, or ranked top 1000 in the world in terms data
size, the scalability reason isn't that strong.

Xah Lee wrote:

> many people mentioned scalibility... though i think it is fruitful to
> talk about at what size is the NoSQL databases offer better
> scalability than SQL databases.
>
> For example, consider, if you are within world's top 100th user of
> database in terms of database size, such as Google, then it may be
> that the off-the-shelf tools may be limiting. But how many users
> really have such massive size of data? note that google's need for
> database today isn't just a seach engine.
>
> It's db size for google search is probably larger than all the rest of
> search engine company's sizes combined. Plus, there's youtube (vid
> hosting), gmail, google code (source code hosting), google blog, orkut
> (social networking), picasa (photo hosting), etc, each are all ranked
> within top 5 or so with respective competitors in terms of number of
> accounts... so, google's datasize is probably number one among the
> world's user of databases, probably double or triple than the second
> user with the most large datasize. At that point, it seems logical
> that they need their own db, relational or not.

Xah
∑ http://xahlee.org/

☄
From: News123 on 14 Mar 2010 10:52
Hi DUncan,


Duncan Booth wrote:
> Xah Lee <xahlee(a)gmail.com> wrote:
>
>> For example, consider, if you are within world's top 100th user of
>> database in terms of database size, such as Google, then it may be
>> that the off-the-shelf tools may be limiting. But how many users
>> really have such massive size of data?
>
> You've totally missed the point. It isn't the size of the data you have
> today that matters, it's the size of data you could have in several years'
> time.
>
> Maybe today you've got 10 users each with 10 megabytes of data, but you're
> aspiring to become the next twitter/facebook or whatever. It's a bit late
> as you approach 100 million users (and a petabyte of data) to discover that
> your system isn't scalable: scalability needs to be built in from day one.


any project/product has to adapt over time.


Not using SQL just because your 20 user application with 100 data sets
might grow into the worlds biggest database doesn't seem right to me.


I strongly believe in not overengineering a product.

For anything I do I use the most covnenient python library first.
This allows me to have results quicky and to get feedback about the
product ASAP.

Lateron I switch to the more performant versions.


bye


N
First  |  Prev  | 
Pages: 1 2 3
Prev: uw-p and make-thread
Next: Hi for those who loves fashion.. check this out :)