{"id":1077,"date":"2011-08-17T13:53:03","date_gmt":"2011-08-17T13:53:03","guid":{"rendered":"http:\/\/www.odbms.org\/blog\/?p=1077"},"modified":"2011-08-17T13:53:03","modified_gmt":"2011-08-17T13:53:03","slug":"on-versants-technology-interview-with-vishal-bagga","status":"publish","type":"post","link":"https:\/\/www.odbms.org\/blog\/2011\/08\/on-versants-technology-interview-with-vishal-bagga\/","title":{"rendered":"On Versant`s technology. Interview with Vishal Bagga."},"content":{"rendered":"

\u201cWe believe that data only becomes useful once it becomes structured.\u201d <\/em>— Vishal Bagga<\/strong><\/p>\n

There is a lot of discussion on NoSQL databases nowdays. But what about object databases<\/em>?
\nI asked a few questions to Vishal Bagga<\/strong>, Senior Product Manager at Versant.<\/a><\/p>\n

RVZ<\/p>\n

Q1. How has Versant’s technology evolved over the past three years?<\/strong><\/p>\n

Vishal Bagga:<\/strong> Versant is a customer driven company. We work closely with our customers trying to understand how we can evolve our technology to meet their challenges – whether it\u2019s regarding complexity, data size or demanding workloads.<\/p>\n

In the last 3 years we have seen 2 very clear trends from our interaction with our new and existing customers \u2013 growing data sizes and increasingly parallel workloads. This is very much in-line with what the general database market is seeing. In addition there was request for simplified database management and monitoring.<\/p>\n

Our state of the art Versant Object Database 8 released last year was designed for exactly these scenarios. We have added increased scalability and performance on multi-core architectures, faster and better defragmentation tools, Eclipse based management and monitoring tools to name a few. We are also re-architecting our database server technology to automatically scale when possible without manual DBA intervention and allow online tuning (reconfigure the database instance online without impacting applications).<\/p>\n

Q2. On December 1, 2008 Versant acquired the assets of the database software business of Servo Software, Inc. (formerly db4objects, Inc.). What happened to db4objects<\/a> since then? How does db4objects fit into Versant technology strategy?<\/strong><\/p>\n

Vishal Bagga:<\/strong> The db4o community is doing well and is an integral part of Versant. In fact, when we first acquired db4o at the end of 2008, there were just short of 50,000 registered members.
\nToday, the db4o community boasts nearly 110,000 members having more than doubled in size in the last 2+ years.
\nIn addition, db4o has had 2 major releases with some significant advances in enterprise type features allowing things like online defragmentation support. In our latest major release, we announced a new data replication capability between db4o and the large scale enterprise class Versant database.
\nVersant sees a great need in the mobile markets for technology like db4o which can play well in the lightweight handheld, mobile computing and machine-to-machine space while leveraging big data aggregation servers like Versant which can handle the huge number of events coming off of these intelligent edge devices.
\nIn the coming year, even greater synergies are being developed and our communities are merging into one single group dedicated to next generation NoSQL 2.0 technology development.<\/p>\n

Q3. Versant database and NoSQL databases: what are the similarities and what are the differences?<\/strong><\/p>\n

Vishal Bagga: <\/strong> The Not Only SQL databases are essentially systems that have evolved out of a certain business need – The need was essentially to have horizontally scalable systems running on commodity hardware with a simple \u201csoft-schema\u201d model for example social networking, offline data crunching, distributed logging system, event processing systems etc.<\/p>\n

Relational databases were considered to be too slow, expensive and difficult to manage and administrate, expensive and difficult to adapt to quick changing models.<\/p>\n

If I look at similarities between Versant and NoSQL, I would say that:<\/p>\n

Both systems have designed around the inefficiency of JOINs. This is the biggest problem with relational databases. If you think about it, in most operational systems relations don\u2019t change e.g. Blog:Article, Order:OrderItem, so why recalculate those relations each time they are accessed using a methodology which gets slower and slower as the amount of data gets larger. JOINs have a use case, but for some 20%, not 100% of the use cases.<\/p>\n

Both systems leverage an architectural shift to a \u201csoft-schema\u201d which allows scale-out capability – the ability to partition information across many physical nodes and treat those nodes as 1 ubiquitous database.<\/p>\n

When it comes to differences:<\/p>\n

The biggest in my opinion is the complexity of the data. Versant allows to you to model very complicated data models seamlessly with ease whereas doing so with a NoSQL solution would be much more effort and you would need to write a lot of code in the application to represent the data model.
\nIn this respect, Versant prefers to use the term \u201csoft-schema\u201d \u2013vs- the term \u201cschemaless\u201d, terms which are often interchanged in discussion.
\nWe believe that data only becomes useful once it becomes structured, in fact that is the whole point of technologies like Hadoop, to churn unstructured data looking for a way to structure it into something useful.
\nNoSQL technologies that bill themselves as \u201cschema-less\u201d are in denial of the fact that they are leaving the application developer the burden of defining the structure and mapping the data into that structure in the language of the application space. In many ways, it is the mapping problem all over again. Plus, that kind of data management is very hard to change it over time, leading to a brittle solution difficult to optimize for more than 1 use case. The use of \u201csoft-schema\u201d lends itself to a more enterprise manageable and extensible system where the database still retains important elements of structure, while still being able to store and manipulate unstructured types.<\/p>\n

Another is the difference in the consistency model. Versant is ACID centric and Versant\u2019s customers depend on this for their mission critical systems \u2013 it would be nearly impossible for these systems to use NoSQL given the relaxed constraints. Versant can do a CAP mode, but that is not our only mode of operation. You use it where it is really needed; you are not forced into using it unilaterally.<\/p>\n

NoSQL systems make you store your data in a way that you can lookup efficiently by a key. But what if want to lookup something differently; it is likely to be terribly inefficient. This may be okay for the design but a lot of people do not realize that this is a big change in mindset. Versant offers a more balanced approach where you can navigate between related objects using references; you can for example define a root object and then navigate your tree from that object. At the same time you can run ad-hoc queries whenever you want to.<\/p>\n

Q4. Big Data: Can Versant database be useful when dealing with petabytes of user data? How?<\/strong><\/p>\n

Vishal Bagga:<\/strong> I don\u2019t see why not. Versant was always designed to work on a network of databases from the very start. Dealing with a Petabyte is really about designing a system with the right architecture. Versant has that architecture just as intact as anyone in the database space saying they can handle a Petabyte. Make no mistake, no matter how you do it, it is a non-trivial task. Today, our largest customer databases are in the 100\u2019s of terrabyte range, so getting to a Petabyte is really a matter of needing that much data.<\/p>\n

Q5. Hadoop is designed to process large batches of data quickly. Do you plan to use Hadoop and leverage components of the Hadoop ecosystem like HBase, Pig, and Hive?<\/strong><\/p>\n

Vishal Bagga:<\/strong> Yes, and some of our customers already do that today. A question for you: \u201cWhy are those layers in existence?\u201d I would say the answer is that most of these early NoSQL 1.0 technologies do not handle real world complexity in information models. So, these layers are built to try and compensate for that fact. That is the exact point where Versant\u2019s NoSQL 2.0 technology fits into the picture, we help people deal with complexity of information models, something that 1st generation NoSQL has not managed to accomplish.<\/p>\n

Q6. Do you think that projects such as JSON<\/a> (JavaScript Object Notation) and MessagePack<\/a> (binary-based efficient object serialization library ) play a role in the odbms market<\/strong>?<\/p>\n

Vishal Bagga:<\/strong> Absolutely. We believe in open standards. Fortunately, you can store any type in an ODBMS. These specific libraries are particularly important for current most popular client frameworks like Ajax. Finding ways to deliver a soft-schema into a client friendly format is essential to help ease the development burden.<\/p>\n

Q7. Looking at three elements: Data, Platform, Analysis, where is Versant heading up?<\/strong><\/p>\n

Vishal Bagga:<\/strong> It is a difficult question as database and data management is increasingly a cross cutting concern. It used to be perfectly fine to keep your Analysis as part of your off-line OLAP systems, but these days there is an increasing push to get Analytics to the real time business.
\nSo, you play with Data, you play with Analytics whether you do it directly or in concert with other technologies through partnership. Certainly, as Versant embraces Platform as a Service, we will do so through eco system partners who are paving the way with new development and deployment methodologies.<\/p>\n

Related Posts<\/strong><\/p>\n

– Objects in Space: \u201cHerschel\u201d the largest telescope ever flown.<\/a> (March 18, 2011)<\/p>\n

– Benchmarking ORM tools and Object Databases.<\/a> (March 14, 2011)<\/p>\n

– Robert Greene on \u201cNew and Old Data stores\u201d <\/a>. (December 2, 2010)<\/p>\n

– Object Database Technologies and Data Management in the Cloud.<\/a> (September 27, 2010)<\/p>\n

##<\/p>\n","protected":false},"excerpt":{"rendered":"

\u201cWe believe that data only becomes useful once it becomes structured.\u201d — Vishal Bagga There is a lot of discussion on NoSQL databases nowdays. But what about object databases? I asked a few questions to Vishal Bagga, Senior Product Manager at Versant. RVZ Q1. How has Versant’s technology evolved over the past three years? Vishal […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":[],"categories":[1],"tags":[66,148,149,239,246,255,327,374,413,427,471,499,553,601,612],"_links":{"self":[{"href":"https:\/\/www.odbms.org\/blog\/wp-json\/wp\/v2\/posts\/1077"}],"collection":[{"href":"https:\/\/www.odbms.org\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.odbms.org\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.odbms.org\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.odbms.org\/blog\/wp-json\/wp\/v2\/comments?post=1077"}],"version-history":[{"count":0,"href":"https:\/\/www.odbms.org\/blog\/wp-json\/wp\/v2\/posts\/1077\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.odbms.org\/blog\/wp-json\/wp\/v2\/media?parent=1077"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.odbms.org\/blog\/wp-json\/wp\/v2\/categories?post=1077"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.odbms.org\/blog\/wp-json\/wp\/v2\/tags?post=1077"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}