tag:blogger.com,1999:blog-6293579155917103664.post4063365536398208796..comments2023-09-05T05:41:31.889-07:00Comments on cloud computing: NoSQL Is Not SQL And That’s A ProblemChirag Mehtahttp://www.blogger.com/profile/08256194832932033050noreply@blogger.comBlogger4125tag:blogger.com,1999:blog-6293579155917103664.post-74215546368818641582010-04-17T15:29:27.515-07:002010-04-17T15:29:27.515-07:00Chirag,
You have laid down the gauntlet we picked...Chirag,<br /><br />You have laid down the gauntlet we picked up two years ago! <br /><br />GenieDB was designed to provide developers, like ourselves, a way of building apps that scale-out invisibly, without us having to worry about eventual consistency after porting parts or all of our applications to webscale / NoSQL architecture. SQL & NoSQL working togther, scaling togther, without changing the way we work... and there's a working GenieDB for MySQL storage engine in Beta to prove our point.<br /><br />I know you saw our #UTR presentation on this very subject. The full details of how we've achieved an engineering solution to the CAP problem are in our whitepapers on www.geniedb.com.<br /><br />Thanks again for your very kind tweets regarding our pitch :). It was tough out there!<br /><br />Very best,<br /><br />Jack Kreindler (Founder, GenieDB)Watchdoghttps://www.blogger.com/profile/08334669530721212301noreply@blogger.comtag:blogger.com,1999:blog-6293579155917103664.post-34673479956711397282010-03-11T02:36:23.391-08:002010-03-11T02:36:23.391-08:00Great Information shared. Technology is very much ...Great Information shared. Technology is very much developed. I am very much interested in computing field, thats why am collecting information about it. I have planned to attend the <a href="http://cloudslam10.com" rel="nofollow">upcoming 2nd Annual Virtual Conference</a> which is going to be hosted online march 2010. I believe i would be benefited much with that cloud computing conference.Unknownhttps://www.blogger.com/profile/07073659061418697210noreply@blogger.comtag:blogger.com,1999:blog-6293579155917103664.post-43451719885359227362010-03-10T23:03:36.008-08:002010-03-10T23:03:36.008-08:00I would like to add a twist to the argument which ...I would like to add a twist to the argument which to me seems to suggest that developers and designers only have a mutually exclusive choice when it comes to RDBMS vs. NoSql. Either fix and design your schema ahead of time and then run around designing/maintaining caching/optimization layers or dump it all in some document-oriented key/value store and then scratch your head when it is time to maintain consistency, transactionality and most importantly-reporting and analytics. I would opine that a more astute architectural approach would be to contextually combine the legacy mentality(and experience)of using pure play RDBMS based data stores with the flexibility and out of the box performance of NoSql engines. Some sort of an approach taken by Content Management Systems that maintain metadata in relational tables while the actual content can be stored in a variety of formats. Now I am no insider to Facebook or Twitter but I doubt that if I purchase virtual currency on Facebook that my information would be dumped in a couchdb/mongodb/hbase powered database or if I view my profile page on Twitter that the information is being dynamically generated from multiple RDBMS tables at runtime.<br />To address the larger theme behind Chirag's original comment '....a developer upfront has to pick persistence, consistency, and access options for an application.....'-I guess one way forward could be to micro-model transactional/analytical metadata requirements into an RDBMS while keeping a NoSql engine for storing 'dataset dumps'. The ingenuity and relative competitive advantage of an application would likely lie in the quality of metadata stores(which presumably would involve much lesser upfront effort that designing an entire RDBMS schema) in such hybrid architecturesDheeraj Saxenahttp://blog.blazebot.comnoreply@blogger.comtag:blogger.com,1999:blog-6293579155917103664.post-4250558346932499442010-03-07T18:47:05.569-08:002010-03-07T18:47:05.569-08:00An excellent article but that left me a little baf...An excellent article but that left me a little baffled about the challenge. Why would you require independence of consistency models as part of the challenge? It seems that given the impossibility of working around the CAP theorem, consistency is the objective chosen to sacrifice (primarily for business reasons) in order to build a working system. So why would building consistency-safe systems for general use be the goal? Are you suggesting that such a system be designed so that it could be used as an application/service by others? Would it not concern the user's how their consistency issues are resolved by the underlying infrastructure?<br /><br />Thanks very much for the writeup!Alok Bhargavahttp://arisdad.tumblr.com/post/433714064/compscibehindinternetbigguysnoreply@blogger.com