Until recently, Relational Databases have been the rage... but now there's a new kid on the block: the NoSQL database. NoSQL databases turn the conventions we've all learned on their heads: data normalization, pivot tables, schemas, and more. Instead of storing metadata and relations across tables, we can create custom schemas per record -- offering incredible flexibility and reducing the number of queries required to get at exactly the information we need. Additionally, another movement has been taking development practices by storm: the idea of using Plain Old PHP Objects as domain entities. By not tying the domain objects directly to the data store backend, developers gain both testability and flexibility. No longer is the domain model tied to an RDBMS solution, allowing usage of NoSQL solutions -- which in many ways are more suited to domain models than their RDBMS counter parts. In this talk, we'll look at some of the advantages and disadvantages of NoSQL databases, as well as some examples of applications that could benefit from the new paradigms they offer.


Comments are closed.

Another great presentation from MWoP. I really want to go try MongoDB now!

My favorite talk of the whole event. I was already sold on document databases but Matthew provided solid case for NoSQL and was an engaging and knowledgable speaker.

Informative view on using alternatives to SQL. I liked the simple examples and comparison with the traditional methods.

Good talk, but lacked depth. More complex examples would make it more interesting. I personally would have liked more about the difference between RDBMS and NoSQL and when to use what. NoSQL has lot's of simple examples where it works great (just blog items with tags and comments), but what about the big projects with 100+ tables in a RDBMS, will they benefit from NoSQL, in which cases and in which cases not? But maybe that's a whole other topic for someone else ;)

Same as richardhimkamp. Loved the presentation's point of view, but would have liked some more complex examples.

Made curious by the presentation of David Zuelke on CouchDB decided to follow this one. The questions that rose from Davids presentation were answered for me here.

I did miss an example of a relation between two different entities or types of documents and the way it should be maintained. Until I find out how this should be done I will not use a document oriented database, but I sure will try to!

Good presentation, felt it would have been better to have it as an hour talk and dig a little deeper into some of the stuff.

Matthew's talk was a great add-on on the couchDB biased talk of David. Both talks where my personally reasons to stay for the saturday events. And it was an afternoon well spend. I see where the fuzz was all about, and yes.. Storing your data as an object in the DB actually makes sense! Sure there are still a few bridges to conquer.

On the personal level, Matthew is a very confident and natural relaxed speaker. Would not mind attending some other talks by him, he has a certain way of peeling the layers down to the part that really matters, the core! Awesome!

Great, introduction to the new NoSQL databases, I enjoyed the way Matthew described the possibilities of these database systems without neglecting the strengths and weaknesses of both.

Covered the basics you needed to know very well. Not much for advanced users but excellent insite for novices. Looking forward to using mongodb!

It is always a pleasure attending a talk by Matthew. This one was particularly clear, not in the least because of the simplicity of the examples.

I also liked it because it clearified the pattern with the database wrapper and the service layer that I partly missed during the tutorial last year, because I wasn't paying enough attention. This was just a side effect, but I was glad I caught up with that.

This talk introduced me to this NoSQL subject, that was mostly new to me. That's exactly why I go to conferences. To get pointed at many, many new things for which you can't spare the time to go activily look for. Thank you Matthew.