SearchYC.com

All of the articles I've read recently talk about the successful migration of very large websites to NoSQL solutions. The argument against are that they NoSQL is only needed for a very small percentage of websites. That coupled with the much larger SQL tools and knowledge base and uncertainty that any new website will need such scaling leads me to my question.

Why not just start with SQL and plan a migrate to a NoSQL solution later, when it's really needed?

It's certainly doable. I feel that the benefit of a NoSQL solution is, at this time, outweighed by the ease of an SQL solution for such a majority of sites that to plan from the beginning for a NoSQL solution is overkill.

Thoughts?

I've been hearing a ton of advantages over using the various nosql solutions (primarily couchdb and mongo). What are the disadvantages to these DBs? Data duplication?

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've tried to read up on NoSQL because I hear so much about it, but I can't really seem to find a synthesis that uses terminology I can understand. What is a relational data store as opposed to a non-relational data store? What advantages does NoSQL confer and how does it achieve those?

I am used to seeing data in tables and their relationship via foreign keys. I would like to move on to noSQL (key-value) store. A challenge to me is how to stop thinking about foreign keys and tables and think everything in a single key-value store. Does anyone point to guide/links how to move away from RDBMS mindset to key-value store mindset. Real life examples of moving rdbms schemas to noSQL would be great.

Long time, first time so be gentle. I just started (4 days ago) a blog about NoSQL databases. The aim is to be a central location for various posts, articles and reference information about all of the various NoSQL technologies out there. Basically, like HighScalability except for NoSQL data stores instead of scalable architectures.

Now I am just a humble developer trying this out for the first time, but I'm wondering if anyone else is interested in blogging about the same stuff because it would be really cool to have another 2-3 authors writing posts.

My email is in my profile so drop me a line and I can point you to the site.

I've recently (1 week ago) started a blog on NoSQL databases. I'm aiming for the site to be like HighScalability.com, but for NoSQL databases instead of scalable architectures.

I wanted feedback on the design, initial content and if you guys could use something like this. Any feedback would be greatly appreciated.

URL: http://nosqldatabases.com

Hi,

I am a new graduate. I will be continuing my education with a masters in CS in University of Cincinnati.

My question is; is .NET knowledge useless?

Everywhere I look, everyone is using * nix + php + nosql/mysql/postgre. By everywhere I mean giants like Facebook, or any startup job post I look at.

I admit I am no expert but I like .NET, particularly C# and MSSQL. I enjoy using Visual Studio, mostly because it lets me create very fast. I love it's support tools like IntelliSense.

Should I switch to php+*nix+nosql, and start learning those?

I was wondering if I could get some feedback on the content and design of my site.

The site is http://www.nosqldatabases.com. As you can imagine the subject matter is about NoSQL data stores.

Any feedback would be greatly appreciated.

Thanks Derek

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?