NoSQL: All content tagged as NoSQL in NoSQL databases and polyglot persistence

NoSQL Databases: The Missing White Paper

About:

NoSQL theory

,

Great piece, getting most of the things right, published on Pythian:

NoSQL databases are a good solution for a specific set of problems. Before choosing NoSQL database make sure you understand the application you are writing and its requirements. Be sure that NoSQL model will work, that it provides value and that you can live with the trade-offs. Make sure you understand the specific NoSQL database that you chose and that it fits your requirements. Make sure you know how to model your data in a way that uses this database in the best way and that you can deploy it in operations without losing sleep. Do your own tests – don’t believe blog posts and benchmarks. Deployed correctly, NoSQL databases are an efficient and reliable solution for a set of non-relational applications. Chosen for the wrong problems or the wrong environment, they will make your life very difficult indeed.

Should replace the ☞ Wikipedia article.

Original title and link: NoSQL Databases: The Missing White Paper (NoSQL databases © myNoSQL)

via: http://www.pythian.com/news/16817/nosql-deep-dive-the-missing-white-paper/

Big Data: What is a BigData Architect?

About:

A recent job announcement on the ☞ NoSQL Google Group stemmed a few hilarious reactions. But I think it would be interesting to answer the question of is there such a thing like a BigData architect? What would be the qualifications of a BigData architect?

Based on this job post (nb I’ve removed most of the buzzwords in the announcement), a BigData architect would have extensive experience dealing with data modeling and data management (both relational and non relational) and designing and operating distributed scalable systems.

Personally, I think BigData is just a relative term: what is big data for a startup will not represent big data for Facebook, Yahoo, or Google. Also, getting from 2 servers up to tens with a couple of people and scaling from tens to thousands with tons of engineering support and budget is just a different “scale”. So, I guess the question remains: what is a BigData architect?

Original title and link: Big Data: What is a BigData Architect? (NoSQL databases © myNoSQL)

NoSQL: Do You Need to Associate Your Product with it?

About:

NoSQL

,

NoSQL database

,

NoSQL theory

,

Mohammad Abdurraafay in a post about Apple Core Data:

My take on Core Data is, because it’s just not being Open Sourced, it’s not filed under NoSql. Otherwise, it’s the only NoSql on the best mobile platform, i.e. iOS and probably the first.

☞ posts.mohammadabdurraafay.com

This seems to be a reoccurring theme for existing storage solutions and not only. And I bet things will get more intense in the near future.

Indeed there are various arguments that can be used to associate your product with NoSQL databases: the data model, the processing model, the lack of SQL, etc. You have a key-value store (e.g. BerkleyDB) it is NoSQL. You have an object database or its new reincarnation as graph database, then you have a NoSQL database. Your product deals with BigData, then it is NoSQL.

But the real question is: if your product is already filling a market need and is well positioned, why would you try to place it under a buzzword umbrella?

Original title and link: NoSQL: Do You Need to Associate Your Product with it? (NoSQL databases © myNoSQL)

NoSQL: 44% Business IT Pros Ask What's That

About:

NoSQL

,

NoSQL database

,

According to an InformationWeek survey:

Heck, 44% of survey respondents hadn’t even heard of NoSQL.

If you think of it, I’d say that percentage is even lower than the reality. Not to mention that except Hadoop, I don’t think there’s any NoSQL adoption in the enterprise world yet.

Original title and link: NoSQL: 44% Business IT Pros Ask What’s That (NoSQL databases © myNoSQL)

via: http://www.informationweek.com/news/business_intelligence/databases/showArticle.jhtml?articleID=227500077

NoSQL CouchDB founder turns to phone and cloud services

About:

NoSQL

,

couchdb

,

mobiles

,

couchio

,

couchone

,

Gavin Clarke (The Register):

NoSQL start-up CouchIO is targeting mobile and clouds after just a year of trying to monetize the company’s CouchDB document store.

[…]

Rather than to replace SQLite, Katz believes that CouchDB has a future by being used in addition to SQLite — primarily on document-centric apps such as email, calendaring, scheduling, contacts, CRM, time sheets, and inventory. “That’s where Couch really shines,” Katz said.

Back to origins?^[1]

Before creating CouchDB, Damien Katz has been working on Lotus Notes. (↩)

Original title and link for this post: NoSQL CouchDB founder turns to phone and cloud services (published on the NoSQL blog: myNoSQL)

via: http://www.theregister.co.uk/2010/09/08/couchone_couchdb_nosql_new_name/

BigData: How Data Strategy Will Change

About:

BigData

,

NoSQL

,

most every company is living in its own version of the Big Data era. Two forces define this era: size and speed. And those forces are driving companies to consider new choices for how they deal with data.

A good read about what drives BigData and where we are heading to. Ignore for a second the company and product names in the article and think where NoSQL databases, distributed filesystems, RDBMS will fit in.

Original title and link for this post: BigData: How Data Strategy Will Change (published on the NoSQL blog: myNoSQL)

via: http://www.hnt-vnpt.com.vn/2010/08/big-data-era-how-data-strategy-will.html

NoSQL databases: 10 Things you Should Know About Them

About:

NoSQL database

,

NoSQL

,

BigData

,

5 pros and 5 cons by Guy Harrison:

Five advantages of NoSQL

Elastic scaling

Big data

Goodbye DBAs (see you later?)

Economics

Flexible data models

Five challenges of NoSQL

Maturity

Support

Analytics and business intelligence

Administration

Expertise

A few amendments though:

Elastic scaling: partially correct. Right now there are just a few featuring elastic scaling: Cassandra, HBase, Riak, Project Voldemort, Membase, and just recently CouchDB through BigCouch.
Big data: partially correct. Some of the NoSQL databases do not scale horizontally and so they are not a perfect fit for BigData.
Goodbye DBAs (see you later?): Maybe you’ll not call them DBA, but someone should still do data modeling and think about data access patterns
Support and Expertise: I do see these just as sub-categories of maturity (lack of thereof).

Original title and link for this post: NoSQL databases: 10 Things you Should Know About Them (published on the NoSQL blog: myNoSQL)

via: http://blogs.techrepublic.com.com/10things/?p=1772

The Future of MySQL

About:

mysql

,

nosql

,

Narayan Newton:

However, things are mostly definitely changing. The trend for the last year has been major developments outside of MySQL AB, funded by everyone from Google to Percona to MontyProgram. In fact, the 5.4 release of MySQL is little more than a re-packaging of external patches. This is a far cry from an earlier MySQL AB driven development model. With Oracle’s purchase of Sun and by extension MySQL AB, this change has accelerated.

Sounds really sad for such a important piece that, as part of LAMP, has pushed the web forward. But I know at least 2 NoSQL databases that will use this opportunity in their favor.

Original title and link for this post: The Future of MySQL (published on the NoSQL blog: myNoSQL)

20 Linux Monitoring Tools for SysAdmins

About:

NoSQL

,

Not only NoSQL:

Need to monitor Linux server performance? Try these built-in command and a few add-on tools. Most Linux distributions are equipped with tons of monitoring. These tools provide metrics which can be used to get information about system activities. You can use these tools to find the possible causes of a performance problem. The commands discussed below are some of the most basic commands when it comes to system analysis and debugging server issues such as:

Finding out bottlenecks.

Disk (storage) bottlenecks.

CPU and memory bottlenecks.

Network bottlenecks.

Original title and link for this post: 20 Linux Monitoring Tools for SysAdmins (published on the NoSQL blog: myNoSQL)

via: http://www.cyberciti.biz/tips/top-linux-monitoring-tools.html

Django and NoSQL Databases Latest Status Update

About:

django

,

nosql

,

Recently, in the Django and NoSQL databases revisited, I’ve covered the coordinated efforts for making Django a NoSQL friendly framework. Alex Gaynor, the main person behind this initiative having the support of the Django community, has ☞ published the final report of the GSOC project:

With this past week GSOC has officially come to it’s close, and I’m here to report on the status of the query-refactor. The original purpose of this branch was to do refactorings to the internals of the ORM, and produce a prototype backend for a non-relational database to demonstrate that this was a viable option. At this time far more work has gone into the latter half of the project, I have developed a fully functioning MongoDB backend, that demonstrates that possibility of using the ORM, almost unmodified on non-relational databases. However, some of the larger refactors that I was originally hoping to do have ultimately not happened, on the other hand they are evidentially not necessary for a functioning backend. At this time there are a number of outstanding tasks, such as: porting the ListField to work on Postgres, and completing the work on embedded documents.
However the largest open question is what of this work should be merged into trunk, and what should live external. My recommendation would be for any changes in Django itself to be merged, including the new form fields, but for the MongoDB backend (and, indeed, any future backends) to live external to Django, until such a time as it obtains a user base anywhere approaching our current backends, as well as a more individuals dedicated to maintaining it.

The guys over ☞ All Buttons Pressed also commented on the outcome of this project:

The biggest design issue (in my opinion) is how to handle AutoField. In the GSoC branch, non-relational model code would always need a manually added NativeAutoField(primary_key=True) because many NoSQL DBs use string-based primary keys. As you can see in Django-nonrel, a NativeAutoField is unnecessary. The normal AutoField already works very well and it has the advantage that you can reuse existing Django apps unmodified and you don’t need a special NativeAutoField definition in your model. Hopefully this issue will get fixed before official NoSQL support is merged into trunk.

Original title and link for this post: Django and NoSQL Databases Latest Status Update (published on the NoSQL blog: myNoSQL)

InformationWeek on MongoDB

About:

NoSQL

,

Informed journalism:

In addition to MongoDB, systems such as CouchDB or Cassandra are in use on social networking and game sites, including Farmville, and online retailing, such as Amazon.com.

[…]

Like other large cluster software, such as Hadoop, MongoDB generates two replicas of the original data set in the server cluster so that it can tolerate a hardware failure