[11:21] <czajkowski> also if anyone would like to learn about MongoDB, there is a free class on it over the coming weeks, self paced and you get  acert at the end of it . https://education.mongodb.com/courses/10gen/M101P/2013_November/about
[11:24] <zmoylan-len> nice
[11:26] <czajkowski> yeah
[11:26] <czajkowski> self paced means you can try it at your own pace which is nice
[11:29] <slashbel> maybe silly question (as i have yet to be sold the idea) but what has mongo got to offer that the likes of mysql/postgres cannot provide?
[11:29]  * slashbel rarely touches databases these days
[11:39] <ebel> slashbel: usually much more scale.
[11:39] <ebel> slashbel: and in theory if you like json-y things
[11:39] <ebel> (though most web apps /should/ have proper db migrations...)
[11:40] <ebel> (I /think/)
[11:42] <slashbel> aye
[11:55] <ebel> y'know, it's like asking "python vs. ruby" :P different types of software
[11:56] <ebel> slashbel: remember, sometimes ACID databases (like MySQL/postgreSQL) can do *too* much
[11:56] <ebel> transactions, etc. *can* slow things down when you don't need transactions
[11:57] <ebel> If you *don't care* about consistancy & atomicity, then you can get speed benefits from ignore them and forcing the app writer to do it.
[11:58] <ebel> Like C++ vs Java. If you don't care about memory management, and are happy with forcing the app developer to deal with it, you can get speed benefits from not including it.