Here is my comparison between the two
PostgreSQL
Tables
DAL
ACID
vertically scales
set-schema
Both
no built-in object model
requires foreign key lookups
requires migrations if schema DOES change
MongoDB
documents
NoSQL
quick reads
horizontally scales
changing-schema
The advantages I see with N
Final thought...
I think if NoSQL were indicated for use with a web2Py app, it might be most
appropriate to replace some, but not all SQL-based tables.
--r.
On May 21, 2010, at 9:31 AM, Thadeus Burgess wrote:
> I also see really no reason to use NoSQL unless you really just don't
> like writi
But Thadeus, NoSQL is much more than moving away from SQL.
It's not that we *want* joins to become an application's task, or that we want
to remove consistency within requests.
The driving forces are in general scalability, availability, & robustness with
enormous amounts of traffic.
For most sit
I also see really no reason to use NoSQL unless you really just don't
like writing SQL... thats why we have ORMs and DALs anyways.
You still have to use FK relationships with document based sets... ie:
with a 4MB document limit, they suggest you split comments for a post
into its own document and
Haha! I enjoy with this jokes in tech slides, they're amusing!
On Fri, May 21, 2010 at 3:02 PM, Timothy Farrell wrote:
> Developers running with scissors!! LOL!!!
>
>
> On 5/20/2010 2:12 PM, szimszon wrote:
>
>> Nice
>>
>> On máj. 20, 19:52, mdipierro wrote:
>>
>>
>>> http://www.scribd.com/doc/
Developers running with scissors!! LOL!!!
On 5/20/2010 2:12 PM, szimszon wrote:
Nice
On máj. 20, 19:52, mdipierro wrote:
http://www.scribd.com/doc/31669670/PostgreSQL-and-NoSQL
Nice
On máj. 20, 19:52, mdipierro wrote:
> http://www.scribd.com/doc/31669670/PostgreSQL-and-NoSQL
7 matches
Mail list logo
