Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

>Most people that push RDBMS solutions try to shoehorn an RDBMS for every possible scenario.

I don't think that's true for well-informed developers in a space where NoSQL is acceptable.

It might be true generally only in the sense that most developers don't know or care about NoSQL and don't like the idea of learning something new. That's to be expected; most of these guys will never leave .NET/Java and the blessed toolkits associated with each. They are corporate programmers and they don't really count.

A well-informed person might make some good social arguments against NoSQL adoption, like the lack of experienced available developers, or the relative immaturity of the respective codebase, or other issues that surround emerging platforms. These arguments will sometimes hold merit.

Otherwise, I don't know why one would be averse to the implementation of a "NoSQL" datastore for information like logs. I know that I've always having logs in the relational db.

I haven't met many experienced, decent developers who shun NoSQL when there is a good technical and environmental atmosphere for its implementation. I don't think it's a widespread thing.



Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: