To begin with im relatively recent towards the Database world, Im graduation with my B.S. in Comp Science this semester and Database Technologies have really caught my attention so ive been studying a lot of T-SQL because I wish to ultimately obtain a SQL Development job (MS SQL server appeared prefer choice at this time since it is increasing)
ANYWAYS, i have heard a lot of hoopla relating to this NOsql movement of Non-relational database management systems. Attempting to keep this and non-subjective as you possibly can i mainly need to know the benefitsOrdrawbacks of NRDBMS's (like Nosql) and when there's a real future inside them. Possibly like a side question, could it be a poor time for you to be studying SQL generally (particularly the standard RDBMS's we're accustomed to). I forsee people adhering with this particular for any very long time, however again.....I have no idea. I'd hate to determine my interest all of a sudden be going for a join in the marketplace.
There's certainly validity towards the NoSQL movement, however i wouldn't be worried about your SQL abilities likely to waste. NoSQL storage architectures were born from the requirement for highly available and scalable data stores that went beyond exactly what a typical relational database could provide. This comes at a price though, and typically that price is guaranteed consistency. This is not always a sizable concern. Within the situation of something similar to Facebook does not have total consistency for some time for such things as your pictures, status updates, etc. As lengthy because they get consistent sooner or later, it's okay. Alternatively finish, take your money. That kind of data store must supply the strong Acidity qualities that the relational database provides.
NoSQL is not something which I see taking around the globe, it's an alternative choice to the most popular approach of RDBMS's so that as with anything else it's it's talents and weak points.
Here is a superb article about them discussed NetFlix.
Others can address the NoSQL specifics much better than I'm able to, but for the 2nd a part of your question (worrying about engaging in SQL if NoSQL begins gaining popularity): I've clients who still use early flat-file based mainframes.
SQL has not even arrived at full transmission yet, which is VERY established in a lot of business processes. The marketplace for SQL development and maintenance will not go away in the near future, and when it begins into it will not be overnight - you will have time for you to discover the Next Large Factor before you are obsolete.
NoSql databases are ideal for storing unstructured data. Think about it as being generation x of Lotus Notes.
I wouldn't leverage a NoSql database for storing a listing of individuals and addresses, as individuals are completely structured and well-known.
However, basically had some dynamic characteristics of some kind (title/value pairs) or something like that an identical which needed lots of pivoting to get at, then I'd seriously consider it. I would even go down that path even when there's structure, however it is not known in advance. For example with dynamic tables.
Nevertheless, whenever we did some critiques captured (March 2010) and that we did not think the condition from the available free NoSql databases needed for serious production. There is lots more to databases than simply putting data in and setting it up out. Automated backup copies, load balancing, solid query tools, consistency checkers, etc are mandatory. We'll reexamine early the coming year.