Cart
[Home] [By Thread] [By Date] [Recent Entries]
On Sat, 2015-03-07 at 17:03 -0500, Simon St.Laurent wrote: > On 03/05/2015 11:20 AM, Peter Hunsberger wrote: > > Without knowing all the details, given relatively unchanging I'd > > likely send up parsing them into a database. > > Yep - this is the answer I keep hearing from people, with the > exception of people who have mixed content and tend to think of it > all as documents. Peter didn't say relational database... although he did mention Hadoop I think. There isn't a single right answer. Sometimes it's about extracting just the bits you need to query and putting just those in some kind of database - relational, NoSQL, SlightlySQL, triple store, XML-native, hybrid, whatever, with no hope of reconstructing the original -- if you need the original, just use it directly. Sometimes it's worth writing custom code - a database importer, for example - for performance reasons. Sometimes some percentage of your queries actually rely on querying markup in mixed content, or on relationships between parts not explicitly stored. So for Roger I'd say that I think the direction I see is more hybrid stores (from Virtuoso to MarkLogic..) and more variation being acceptable as people come to recognize that different needs are best served with different technologies. -- Liam R. E. Quin <liam@w...> The World Wide Web Consortium (W3C) .signature: no such file or directory
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] |
