RE: sheltered little world i live in -> NODB?

I think we'd all agree that any of the "nosql" implementations are the correct 
choice for 'some' applications?

But this all goes back to the earlier points that have mentioned several times 
now that people designing systems need to know (and plan) for the data they are 
generating, capturing and reporting on before they decide how they want to 
store it - I would imagine that the 'best' solution is often a hybrid one with 
different implementations for different types of data.

It *always* goes back to the data and how it's going to be generated and used. 
Right or no? 

Chris Taylor

"Quality is never an accident; it is always the result of intelligent effort."
-- John Ruskin (English Writer 1819-1900)

Any views and/or opinions expressed herein are my own and do not necessarily 
reflect the views of Ingram Industries, its affiliates, its subsidiaries or its 
employees. 


-----Original Message-----
From: oracle-l-bounce@xxxxxxxxxxxxx [mailto:oracle-l-bounce@xxxxxxxxxxxxx] On 
Behalf Of Coll-Barth, Michael
Sent: Friday, May 18, 2012 10:05 AM
To: oracle-l@xxxxxxxxxxxxx
Subject: RE: sheltered little world i live in -> NODB? 

I couldn't agree with you more.  And don't even get me started with the NoSQL 
movement.  But on the bright side, Java may finally die.  I see people's faces 
when we discuss what to use on such and such new project.
I saw a director actually flinch when Java was mentioned.


--
http://www.freelists.org/webpage/oracle-l




--
http://www.freelists.org/webpage/oracle-l


Other related posts: