[email protected] (Shmuel Metz  , Seymour J.) writes:
> Is that anything like thin film replacing core? Or bubbles?
>
> Predicting that that a technology will be supplanted is easy.
> Accurately predicting what will replace it and when is hard.

lot of DBMS are disk-centric and based on the home position for data is
located on disk ... and real memory/storage is used to cache records.

with increase in real memory sizes, lots of databases can completely fit
in real storage. there has been work on "in memory" databases ... big
motivation was the telco industry ... being able to handle call record
volumes. there were some benchmarks of these "in memory" databases that
might use disks for sequential writing involving logging/recovery ...
against standard DBMS that had enough memory/storage to completely cache
the full DBMS ... and the "in memory" database still got ten times the
thruput ... than disk-centric DBMS (even with all data cached).

In the middle/late 90s, there was prediction that the telcos would take
over the payment industries ... because the telcos were the only
operations (based on scaleup to handle call-record volumes) that were
capable of handling the predicted volumes in micro-payments. Once firmly
entrenched handling micro-payment volumes ... they would then move
upstream to take over the rest of the payment industry. Well, the
micro-payment volumes never materialized ... and the telco industry has
yet to take over the payment industry.

However since then, Oracle has acquired at least one of the "in-memory"
DBMS implementations ... and some of the payment processors have
deployed backend platforms originally developed to handle the telco call
record volumes.

-- 
virtualization experience starting Jan1968, online at home since Mar1970

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

Reply via email to