I do not see any advantages to what your propose over what an RDBMS offers. There is more to the story than just storing and retrieving data. $Clients want the data pivoted into all arrangements of reports. Standards such as PCI compliance shun using Personally Identifiable Information as non-encrypted keys. And then you have technologies such as Hadoop can perform map/reduce algorithms on flat files that span across multiple machines.
What you have sounds cool, but not at the expense of ignoring current solutions that take a lot more into consideration than what you have here. What would sound cooler is a deploy-able implementation of what you propose -- and i certainly hope you don't limit your audience to just 1 platform.
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|