The final cloud-like computing theme contributing to the unfortunate fog around the notion of “big data” is JSON (http://www NULL.json NULL.org/). In my opinion, enterprise consumers of big data solutions built with NOSQL databases aren’t going to be able to connect the dots from the presentation on the JSON open-source project homepage.
More intelligible information about JSON for the non programmer can be found on the web site of the Apache™ CouchDB project (http://couchdb NULL.apache NULL.org/). “CouchDB is a database that completely embraces the web. Store your data with JSON documents. Access your documents and query your indexes with your web browser, via HTTP” (quoted from the first sentence of editorial content published on the site). Quering indexes with your web browser, hmmm . . . might this have something with Chrome’s Omnibox (https://www NULL.google NULL.com/search?sourceid=chrome-psyapi2&ion=1&espv=2&ie=UTF-8&q=omnibox%20json)? In fact, as any reader following the link just provided will note, it does.
So now with this flexibility in mind, it might provide enterprise computing consumers with more of a rationale for calling for the implementation of databases conforming to JSON, which will lend themselves to analytics built with NOSQL tools. If the process of collecting data on some aspect of a business process can be reduced down to little more than punching some keywords into Chrome’s Omnibox (a version of which is now available for Firefox and Internet Explorer), then Lines of Business (LoBs) can count on their personnel getting to the data they need, when they need it, from any device (mobile, desktop, laptop) whenever they need it without the need for any proprietary solution.
Pretty cool. The cool factor increases when one reads more about the CouchDB project. JSON represents an alternative to XML, which requires substantially more verbosity (meaning lines of code) to express the same programming statement. Lots of lines of code contribute to a slower web, where pages can take forever to load. So the comparatively lighter weight promised by using JSON to express steps in a program makes a lot of sense. The intention of JSON and XML are the same, namely to provide a method of data exchange (http://www NULL.idealware NULL.org/articles/data_exchange_alpha_soup NULL.php).
JSON produces “JSON Documents”. Here’s an example of what IBM© is doing with JSON: Search JSON documents with Informix (https://www NULL.ibm NULL.com/developerworks/community/blogs/idsdoc/entry/search_json_documents_with_informix?lang=en).
Ira Michael Blonder
© IMB Enterprises, Inc. & Ira Michael Blonder, 2014 All Rights Reserved