SearchYC.com

What's the current state of NoSQL ? Is it ready to replace SQL ? Should I better stick with an ORM + hand written SQL for my next app or should I consider trying a NoSQL database ? Combination of both ? Share your thoughts !

I have trouble wrapping my head around NoSQL. Maybe because relational databases seem so natural to me?

Anyone have a good introduction to NoSQL style databases? When it's appropriate to use them, (dis)advantages of using them, how to query? Ideally a tutorial of how to build a simple app?

Back in the early 2000s it seemed like your choices for database-driven web sites were MySQL, PGSQL, BerkleyDB (for the Perlites) and maybe SQLite. Enterprises had their Oracle and SQL Server.

Now, when trying to get stuck into a bit of NoSQL/schema-free/document store databases for the web, I am overwhelmed by the number of options, and am struggling to understand the best one for the job.

Do people genuinely believe that the world needs this many NoSQL systems, or are we just in the infancy/resurgence of schema-free, and things are yet to settle down?

you are ninja-esque in your .net skills, but have been moving to more interesting tech (python, nosql/couchdb, erlang).

current candidates are (in no particular order):

bespin, couchdb

what else?

There is much talk of scaling, noSql and functional languages. I wonder if we are just looking at shining new things and not being pragmatists.

Does MySql/Postgresql coupled with dynamically typed languages (Ruby/Python/Groovy) solve 80% of IT problems?

We are holding a Meetup/Mini-Conference in NY this coming Monday, October 5.

Full details are at: http://anyvite.com/events/home/1aczrvxjp6 including RSVP, which we request you please use so we don't flood our rented venue.

I know there's an upcoming NoSQL East conference in Atlanta at end of October, we had started planning and announcing this several months ago. Unfortunately, tracking down space and getting everything organized took a bit more time. We have finally nailed down a larger space to hold this in, and hope that despite the short notice some of you HNers would care to join us.

The idea here is a short meetup and learning; it's not always easy to duck out of work for a tech conference so we hope a few hours out of your evening will leave you feeling enlightened.

Speakers will be covering CouchDB, MongoDB (and a panel with representatives of both projects comparing and contrasting the at-the-surface-similar systems), AllegroGraph RDF Store and using Clojure with Hadoop.

We also are looking for people to present lightning talks on NoSQL topics, so if you have a 5 minute talk in mind that covers a NoSQL technology you think people should see, use cases, examples of projects you've deployed tech (or even replacing MySQL, Sybase, Oracle etc with a NoSQL system) please email me (Link to my "lightning talk signup' mail bucket is on the anyvite page).

Also, huge thanks goes out to 10Gen <http://www.10gen.com> who has done the legwork for securing and renting a venue for this event.

There are plenty of public complaints about SQL lately, and there were some hot discussions here on HN about SQL/NOSQL.

I have a toy project in Haskell, an in-memory DB implementing some limited subset of SQL and transaction support. I started doing this to first learn more about STM, then lightweight threading (forkIO). I implemented JDBC binding too, and can use it from Java.

Every time stumbling upon the SQL/NOSQL debate I feel myself a dinosaur: I work on SQL DB and there are some folks in the Valley who have a periodical meetup against SQL. The question is: if not SQL then what? What are the problems with SQL (I'm not addressing particular SQL implementation problems and standards compliance here, just the language implementing relational algebra per se)?

For example, document-oriented DBs look nice, but what's the fundamental advantage? Key-value stores look oversimplified to me. Any other approaches I missed?