This sounds more like high-throughput external analytics, aka they
will know all the queries consumers will use. This isn't for internal
analytics.
On Sat, Jul 10, 2010 at 10:33 AM, Marty Greenia <martygreenia@gmail.com> wrote:
> It almost seems counter-intuitive. For analytics, you'd think they'd want a
> database that supports more sophisticated query functionality (sql). Whereas
> for everyday tweet storage, something fast and high-throughput (cassandra)
> makes sense.
>
> I'd be curious to here the details as well.
>
> On Sat, Jul 10, 2010 at 10:25 AM, S Ahmed <sahmed1020@gmail.com> wrote:
>>
>> Nice link.
>> From what I understood, they are not using it to store tweets but rather
>> will use mysql? I wish they went into more detail as to why...
>>
>> On Sat, Jul 10, 2010 at 1:25 AM, Kochheiser,Todd W - TOK-DITT-1
>> <twkochheiser@bpa.gov> wrote:
>>>
>>> A good read.
>>>
>>> http://techcrunch.com/2010/07/09/twitter-analytics-mysql/
>>>
>>> Todd
>
>
--
Dan Di Spaltro
|