There is a very small list of people on this planet that likely have an answer to that question....but before I answered, I wanted to do a bit of reading up on these 'No-SQL' DB's to see what all the fuss is about, never having seen or worked with one, I needed to educate myself a bit :). So, I read the article you mentioned, noticing that it is a VERY generic article, showing all sorts of wonderful stats about why MongoDB is better than its competitors...reading a stat sheet on a 'vendor's' website that touts it's better than others is hardly surprising...so I Googled a bit and found this article interesting to describe the difference between SQL and NoSQL DB's.
http://www.neonrain.com/blog/mysql-vs-mongodb-relational-and-non-relational-databases A key point that I read in that article discusses structured vs non-structured schemas. I've been working with one SQL DB or another for going on 20 years or so...so I consider myself fairly educated on the Relational DB realm. I have also been programming in Java for ~6 years, and I consider myself fairly well versed in 'Object Oriented Programming'....now, my familiarity with OOP, helps me understand NoSQL structures a bit better than I think I would likely be able to without a bit more study....so, with all of that said... I'm not entirely sure that 'Remedy' fits into the 'NoSQL' bucket very well...it's not really a matter of programming a version of Remedy that can store data in a MongoDB...but an architectural decision as to if that even makes sense. When I think of say....an Incident, or any Remedy form for that matter, it's very 'structured', and relies on that underpinning structure to keep the framework. Moving in a direction of NoSQL structure, I'm not sure that it would be 'Remedy as we know it' anymore...it would be something else entirely. I'm not saying that would be a bad thing, but it would be a fundamental shift I think. So, with that in mind...I have NO IDEA what BMC is going to do in this space, if anything. Relational DB's have been around for 30+ years, and aren't going away any time soon....so I'm not sure if BMC will feel any need to move in that direction any time soon :) On Sat, Mar 22, 2014 at 10:17 AM, Francois Seegers < [email protected]> wrote: > ** > > Hi All, > > > > Just wanted to know from ya all how you think BMC is going to position our > Remedy space to support the new NoSQL database initiatives if any J > > > > http://www.mongodb.com/leading-nosql-database > > > > Thanks > > Francois > > Email: [email protected] | Mobile: +27 (0)82 799 8710 > Blue Turtle Technologies > > [image: http://www.blueturtle.co.za/images/blue-turtle02.gif] > > > > ------------------------------ > > Blue Turtle Technologies (Pty) Limited | Reg. no.: 2003/002610/07 | > http://www.blueturtle.co.za > Gauteng : Tel: +27 (0)11 206 5600 | Fax: +27 (0)86 208 0237 | Midridge > Office Estate, International Business Gateway, cnr New Road & Sixth Street, > Midrand, 1685 | P O Box 31331, Kyalami, 1684 > Western Cape: Tel: +27 (0)87 702 1867 | Fax: +27 (0)21 552 7764 | Unit > E6, Century Square, Heron Crescent, Century City, Cape Town, 7446 > > DISCLAIMER: This email and any files transmitted with it are confidential > and are intended solely for the use of the individual or entity to whom > they are addressed. This communication represents the originator's personal > views and opinions, which do not necessarily reflect those of Blue Turtle > Technologies (Pty) Ltd. If you are not the original recipient or the person > responsible for delivering the email to the intended recipient, be advised > that you have received this email in error, and that any use, > dissemination, forwarding, printing, or copying of this email is strictly > prohibited. If you received this email in error, please immediately notify > the sender. Thank you. > _ARSlist: "Where the Answers Are" and have been for 20 years_ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years"
<<inline: image001.gif>>
