http://louisgray.disqus.com/A Silicon Valley Blog for Early Adopters and Tech GeeksenSun, 10 Feb 2008 12:31:00 -0000http://blog.louisgray.com/2008/02/assetbar-proposes-solution-to-twitter.html#comment-429216845<p>Better database writing quite misses the point. Messages need to be filtered BEFORE they ever hit the database. Complex event/stream processing (e.g., Coral8 or StreamBase) is the way to do that. I thought that had been settled weeks ago. ::sigh::<br><br>Anyhow, here's my most recent write-up on the subject.<br><br><a href="http://www.texttechnologies.com/2008/02/09/scalable-twitter/" rel="nofollow noopener" target="_blank" title="http://www.texttechnologies.com/2008/02/09/scalable-twitter/">http://www.texttechnologies...</a><br><br>CAM</p>Curt MonashSun, 10 Feb 2008 12:31:00 -0000http://blog.louisgray.com/2008/02/assetbar-proposes-solution-to-twitter.html#comment-429216847<p>A question from one who is not a technical expert on such things. How does the AssetBar solution <a href="http://mrontemp.blogspot.com/2008/02/starling-and-assetbar-comparative-views.html" rel="nofollow noopener" target="_blank" title="http://mrontemp.blogspot.com/2008/02/starling-and-assetbar-comparative-views.html">compare</a> with the Starling solution that Twitter themselves released about a month ago? Are they two different approaches to performance improvement?</p>Ontario EmperorSat, 09 Feb 2008 01:20:00 -0000