Can there be comparation which NoSQL is made for what purpose?

I am especially thinking about querying great deal of data practically read-only.

Edit: I am talking about comparation between NoSQL databases not about comparation with SQL databases.

Soft NoSQL Systems: [not the initial aim of "NoSQL" but mostly worth a search for great non relational solutions] Object Databases

db4o: API: Java, C#, .Internet Langs, Protocol: language, Query Method: QBE (by Example), Soda, Native Queries, LINQ (.Internet), Replication: db4o2db4o &lifier dRS to relationals, Designed in: Java, Cuncurrency: Acidity serialized, Misc: embedded lib, Links: DZone Refcard #53 », Book »,

Versant: Languages/Protocol: Java, C#, C++, Python. Schema: language class model (easy changable). Modes: always consistent and finally consistent Replication: synchronous fault tolerant and peer to see asynchronous. Concurrency: positive and object based locks. Scaling: can also add physical nodes on fly for scale out/in and migrate objects between nodes without impact to application code. Misc: MapReduce via parallel SQL like query across logical database types.

Objectivity: Languages: Java, C#, C++, Python, Smalltalk, SQL access through ODBC. Schema: native language class model, direct support for references, interoperable across all language bindings. 64 bit unique object ID (OID) supports multi exa-byte. Platforms: 32 and 64 bit Home windows, Linux, Macosx, *Unix. Modes: always consistent (Acidity). Concurrency: locks at cluster of objects (container) level. Scaling: unique distributed architecture, dynamic addition/elimination of clients &lifier servers, cloud atmosphere ready. Replication: synchronous with quorum fault tolerant across peer to see partitions.

[Gem, Progress ]

Perst: API: Java,Java ME,C#,Mono. Query method: OO via Perst collections, QBE, Native Queries, LINQ, native full-text search, JSQL Replication: Async+sync (master-slave) Designed in: Java, C#. Caching: Object cache (LRU, weak, strong), page pool, in-memory database Concurrency: Pessimistic+positive (MVCC) + async or sync (Acidity) Index types: Many tree models + Time Series. Misc.: Embedded lib., file encryption, automatic recovery, native full text search, on-line or off-line backup.

ZODB: API: Python, Protocol: Internal, ZEO, Query Method: Direct object access, zope.catalog, gocept.objectquery, Replication: ZEO, ZEORAID, RelStorage Designed in: Python, C Concurrency: MVCC, License: Zope Public License (OSI approved) Misc:Utilized in production since 1998

NEO: API: Python - ZODB "Storage" interface, Protocol: native, Query Method: transactional key-value, Replication: native, Designed in: Python, Concurrency: MVCC at ZODB level, License: GPL "v2 or later", Misc: Load balancing, fault tolerant, hot-extensible.

StupidDB », KiokuDB » (Perl solution),

I discovered this nice listing of NoSQL's at:

If you see just a little past half way lower the page there is a nice listing of noSQL's and appearance to enter detail about each.

I believe that you simply greatly underestimate the energy of RDBMS. Why would you use noSQL?

I have done ~10tb databases.. which was 8 years back, on ancient hardware in comparison to today.

You may not convey more than 10tb of information? Could it be correctly stabilized?

I'm able to scan against a billion rows in SQL and provides instant solutions to just about anything I want.