<?xml version="1.0" encoding="UTF-8"?>
 <rdf:RDF xmlns="http://purl.org/rss/1.0/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:cc="http://web.resource.org/cc/" xmlns:syn="http://purl.org/rss/1.0/modules/syndication/" xmlns:admin="http://webns.net/mvcb/">
  <channel rdf:about="http://pinboard.in">
    <title>Pinboard (jm)</title>
    <link>https://pinboard.in/u:jm/public/</link>
    <description>recent bookmarks from jm</description>
    <items>
      <rdf:Seq>	<rdf:li rdf:resource="https://engineering.linkedin.com/blog/2022/real-time-analytics-on-network-flow-data-with-apache-pinot"/>
	<rdf:li rdf:resource="https://engineering.riotgames.com/news/determinism-league-legends-introduction"/>
	<rdf:li rdf:resource="http://jvns.ca/blog/2016/02/09/til-clock-skew-exists/"/>
	<rdf:li rdf:resource="https://samsaffron.com/archive/2015/12/29/websockets-caution-required"/>
	<rdf:li rdf:resource="https://amplitude.com/blog/2015/08/25/scaling-analytics-at-amplitude/"/>
	<rdf:li rdf:resource="http://blog.acolyer.org/2015/06/15/twitter-heron-stream-processing-at-scale/"/>
	<rdf:li rdf:resource="https://blog.twitter.com/2015/flying-faster-with-twitter-heron"/>
	<rdf:li rdf:resource="http://betterembsw.blogspot.ie/2014/09/a-case-study-of-toyota-unintended.html?m=1"/>
	<rdf:li rdf:resource="http://gotocon.com/dl/goto-berlin-2014/slides/MartinThompson_AeronTheNextGenerationInOpenSourceHighPerformanceMessaging.pdf"/>
	<rdf:li rdf:resource="https://www.linkedin.com/pulse/article/20141106180403-2945786-announcing-confluent-a-company-for-apache-kafka-and-realtime-data"/>
	<rdf:li rdf:resource="http://www.michael-noll.com/blog/2014/10/01/kafka-spark-streaming-integration-example-tutorial/"/>
	<rdf:li rdf:resource="http://sourceforge.net/projects/ccfreaks/files/papers/LeftRight/leftright-extended.pdf"/>
	<rdf:li rdf:resource="https://blog.twitter.com/2014/fighting-spam-with-botmaker"/>
	<rdf:li rdf:resource="http://www.slideshare.net/tantrieuf31/real-time-analytics-with-netty-storm-kafka"/>
	<rdf:li rdf:resource="https://news.ycombinator.com/item?id=7711974"/>
	<rdf:li rdf:resource="https://speakerdeck.com/pyconslides/scaling-realtime-at-disqus-by-adam-hitchcock"/>
	<rdf:li rdf:resource="http://yahooeng.tumblr.com/post/65453012905/introducing-samoa-an-open-source-platform-for-mining"/>
	<rdf:li rdf:resource="http://reverbrain.com/grape/"/>
	<rdf:li rdf:resource="http://www.edn.com/design/automotive/4423428/Toyota-s-killer-firmware--Bad-design-and-its-consequences"/>
	<rdf:li rdf:resource="http://www.slideshare.net/ashleywbrown/storm-at-spiderio-london-storm-meetup-20130618"/>
	<rdf:li rdf:resource="https://www.facebook.com/notes/facebook-engineering/wormhole-pubsub-system-moving-data-through-space-and-time/10151504075843920"/>
	<rdf:li rdf:resource="http://www.infoq.com/interviews/ennis-events"/>
	<rdf:li rdf:resource="https://developers.google.com/drive/realtime/"/>
	<rdf:li rdf:resource="http://engineering.twitter.com/2012/08/trident-high-level-abstraction-for.html"/>
	<rdf:li rdf:resource="http://nathanmarz.com/blog/how-to-beat-the-cap-theorem.html"/>
	<rdf:li rdf:resource="http://www.slideshare.net/nathanmarz/storm-distributed-and-faulttolerant-realtime-computation"/>
	<rdf:li rdf:resource="https://github.com/nathanmarz/storm/wiki/Rationale"/>
	<rdf:li rdf:resource="http://www.slideshare.net/nathanmarz/the-secrets-of-building-realtime-big-data-systems"/>
	<rdf:li rdf:resource="http://russ.garrett.co.uk/2010/01/10/semi-realtime-satellite-desktop-backgrounds/"/>
	<rdf:li rdf:resource="http://dashes.com/anil/2009/07/the-pushbutton-web-realtime-becomes-real.html"/>
      </rdf:Seq>
    </items>
  </channel><item rdf:about="https://engineering.linkedin.com/blog/2022/real-time-analytics-on-network-flow-data-with-apache-pinot">
    <title>Real-time analytics on network flow data with Apache Pinot</title>
    <dc:date>2022-09-14T17:05:24+00:00</dc:date>
    <link>https://engineering.linkedin.com/blog/2022/real-time-analytics-on-network-flow-data-with-apache-pinot</link>
    <dc:creator>jm</dc:creator><description><![CDATA[LinkedIn are using Pinot for this use case, with a super-low-latency querying requirement:

<blockquote>InFlow requires storage of tens of TBs of data with a retention of 30 days. To support its real-time troubleshooting use case, the data must be queryable in real-time with sub-second latency so that engineers can query the data without any hassles during outages. For the storage layer, InFlow leverages Apache Pinot.</blockquote>

]]></description>
<dc:subject>pinot latency metrics linkedin network-flows realtime analytics storage</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jm/b:d408bc8a0e1e/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:pinot"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:latency"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:metrics"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:linkedin"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:network-flows"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:realtime"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:analytics"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:storage"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://engineering.riotgames.com/news/determinism-league-legends-introduction">
    <title>Determinism in League of Legends</title>
    <dc:date>2017-06-21T10:43:57+00:00</dc:date>
    <link>https://engineering.riotgames.com/news/determinism-league-legends-introduction</link>
    <dc:creator>jm</dc:creator><description><![CDATA[Once again, deterministic replay/reruns of online games proves useful.  John Carmack wrote a .plan about this many years ago: https://raw.githubusercontent.com/ESWAT/john-carmack-plan-archive/master/by_day/johnc_plan_19981014.txt

(via Nelson)]]></description>
<dc:subject>clock realtime time determinism testing replay games league-of-legends via:nelson</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jm/b:14fb1751e281/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:clock"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:realtime"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:time"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:determinism"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:testing"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:replay"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:games"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:league-of-legends"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:via:nelson"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://jvns.ca/blog/2016/02/09/til-clock-skew-exists/">
    <title>TIL: clock skew exists</title>
    <dc:date>2016-02-10T15:48:45+00:00</dc:date>
    <link>http://jvns.ca/blog/2016/02/09/til-clock-skew-exists/</link>
    <dc:creator>jm</dc:creator><description><![CDATA[good roundup of real-world clock skew links]]></description>
<dc:subject>clocks clock-skew ntp realtime time bugs distcomp reliability skew</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jm/b:9eea6afc942d/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:clocks"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:clock-skew"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:ntp"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:realtime"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:time"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:bugs"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:distcomp"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:reliability"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:skew"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://samsaffron.com/archive/2015/12/29/websockets-caution-required">
    <title>WebSockets, caution required!</title>
    <dc:date>2016-01-03T10:20:18+00:00</dc:date>
    <link>https://samsaffron.com/archive/2015/12/29/websockets-caution-required</link>
    <dc:creator>jm</dc:creator><description><![CDATA[This, so much. 

<blockquote>There are very valid technical reasons many of the biggest sites on the Internet have not adopted them. Twitter use HTTP/2 + polling, Facebook and Gmail use Long Polling. Saying WebSockets are the only way and the way of the future, is wrongheaded. HTTP/2 may end up winning this battle due to the huge amount of WebSocket connections web browsers allow, and HTTP/3 may unify the protocols</blockquote>

]]></description>
<dc:subject>http realtime websockets long-polling http2 protocols transport web internet</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jm/b:c7af3e72be13/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:http"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:realtime"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:websockets"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:long-polling"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:http2"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:protocols"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:transport"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:web"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:internet"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://amplitude.com/blog/2015/08/25/scaling-analytics-at-amplitude/">
    <title>Scaling Analytics at Amplitude</title>
    <dc:date>2015-08-31T14:06:02+00:00</dc:date>
    <link>https://amplitude.com/blog/2015/08/25/scaling-analytics-at-amplitude/</link>
    <dc:creator>jm</dc:creator><description><![CDATA[Good blog post on Amplitude's lambda architecture setup, based on S3 and a custom "real-time set database" they wrote themselves.

antirez' comment from a Redis angle on the set database: http://antirez.com/news/92

HN thread: https://news.ycombinator.com/item?id=10118413]]></description>
<dc:subject>lambda-architecture analytics via:hn redis set-storage storage databases architecture s3 realtime</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jm/b:cb0a1f26939e/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:lambda-architecture"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:analytics"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:via:hn"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:redis"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:set-storage"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:storage"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:databases"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:architecture"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:s3"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:realtime"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://blog.acolyer.org/2015/06/15/twitter-heron-stream-processing-at-scale/">
    <title>Adrian Colyer reviews the Twitter Heron paper</title>
    <dc:date>2015-06-15T16:04:27+00:00</dc:date>
    <link>http://blog.acolyer.org/2015/06/15/twitter-heron-stream-processing-at-scale/</link>
    <dc:creator>jm</dc:creator><description><![CDATA[ouch, really sounds like Storm didn't cut the muster.  'It’s hard to imagine something more damaging to Apache Storm than this. Having read it through, I’m left with the impression that the paper might as well have been titled “Why Storm Sucks”, which coming from Twitter themselves is quite a statement.'

If I was to summarise the lessons learned, it sounds like: backpressure is required; and multi-tenant architectures suck.

Update: response from Storm dev ptgoetz here: http://blog.acolyer.org/2015/06/15/twitter-heron-stream-processing-at-scale/#comment-1738]]></description>
<dc:subject>storm twitter heron big-data streaming realtime backpressure</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jm/b:39ffe9705551/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:storm"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:twitter"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:heron"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:big-data"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:streaming"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:realtime"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:backpressure"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://blog.twitter.com/2015/flying-faster-with-twitter-heron">
    <title>Twitter ditches Storm</title>
    <dc:date>2015-06-04T10:04:02+00:00</dc:date>
    <link>https://blog.twitter.com/2015/flying-faster-with-twitter-heron</link>
    <dc:creator>jm</dc:creator><description><![CDATA[in favour of a proprietary ground-up rewrite called Heron.  Reading between the lines it sounds like Storm had problems with latency, reliability, data loss, and supporting back pressure.]]></description>
<dc:subject>analytics architecture twitter storm heron backpressure streaming realtime queueing</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jm/b:8bb89823ffcc/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:analytics"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:architecture"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:twitter"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:storm"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:heron"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:backpressure"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:streaming"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:realtime"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:queueing"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://betterembsw.blogspot.ie/2014/09/a-case-study-of-toyota-unintended.html?m=1">
    <title>A Case Study of Toyota Unintended Acceleration and Software Safety</title>
    <dc:date>2015-01-16T22:33:37+00:00</dc:date>
    <link>http://betterembsw.blogspot.ie/2014/09/a-case-study-of-toyota-unintended.html?m=1</link>
    <dc:creator>jm</dc:creator><description><![CDATA[I drive a Toyota, and this is scary stuff.  Critical software systems need to be coded with care, and this isn't it -- they don't even have a bug tracking system! 

<blockquote>Investigations into potential causes of Unintended Acceleration (UA) for Toyota vehicles have made news several times in the past few years. Some blame has been placed on floor mats and sticky throttle pedals. But, a jury trial verdict was based on expert opinions that defects in Toyota's Electronic Throttle Control System (ETCS) software and safety architecture caused a fatal mishap.  This talk will outline key events in the still-ongoing Toyota UA litigation process, and pull together the technical issues that were discovered by NASA and other experts. The results paint a picture that should inform future designers of safety critical software in automobiles and other systems. </blockquote>

]]></description>
<dc:subject>toyota safety realtime coding etcs throttle-control nasa code-review embedded</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jm/b:e6e6d56be7de/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:toyota"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:safety"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:realtime"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:coding"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:etcs"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:throttle-control"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:nasa"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:code-review"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:embedded"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://gotocon.com/dl/goto-berlin-2014/slides/MartinThompson_AeronTheNextGenerationInOpenSourceHighPerformanceMessaging.pdf">
    <title>&quot;Aeron: High-Performance Open Source Message Transport&quot; [slides, PDF]</title>
    <dc:date>2014-11-12T10:08:56+00:00</dc:date>
    <link>http://gotocon.com/dl/goto-berlin-2014/slides/MartinThompson_AeronTheNextGenerationInOpenSourceHighPerformanceMessaging.pdf</link>
    <dc:creator>jm</dc:creator><description><![CDATA[a new networked pub/sub library from Martin "Disruptor" Thompson, based around a replicated, persistent log of messages, with exceptionally low latency.  Apache-licensed.  Very similar to the realtime messaging stack we've built in Swrve. ;)

https://github.com/real-logic/Aeron]]></description>
<dc:subject>realtime messaging pub-sub ipc queues transports martin-thompson slides latencies open-source java libraries</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jm/b:63cce56da5d7/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:realtime"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:messaging"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:pub-sub"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:ipc"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:queues"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:transports"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:martin-thompson"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:slides"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:latencies"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:open-source"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:java"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:libraries"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://www.linkedin.com/pulse/article/20141106180403-2945786-announcing-confluent-a-company-for-apache-kafka-and-realtime-data">
    <title>Announcing Confluent, A Company for Apache Kafka And Realtime Data</title>
    <dc:date>2014-11-06T20:41:44+00:00</dc:date>
    <link>https://www.linkedin.com/pulse/article/20141106180403-2945786-announcing-confluent-a-company-for-apache-kafka-and-realtime-data</link>
    <dc:creator>jm</dc:creator><description><![CDATA[Jay Kreps, Neha Narkhede, and Jun Rao are leaving LinkedIn to form a Kafka-oriented realtime event processing company]]></description>
<dc:subject>realtime event-processing logs kafka streaming open-source jay-kreps jun-rao confluent</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jm/b:5d37bc318bf2/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:realtime"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:event-processing"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:logs"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:kafka"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:streaming"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:open-source"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:jay-kreps"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:jun-rao"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:confluent"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.michael-noll.com/blog/2014/10/01/kafka-spark-streaming-integration-example-tutorial/">
    <title>Integrating Kafka and Spark Streaming: Code Examples and State of the Game</title>
    <dc:date>2014-10-06T15:21:27+00:00</dc:date>
    <link>http://www.michael-noll.com/blog/2014/10/01/kafka-spark-streaming-integration-example-tutorial/</link>
    <dc:creator>jm</dc:creator><description><![CDATA[<blockquote>Spark Streaming has been getting some attention lately as a real-time data processing tool, often mentioned alongside Apache Storm. [...] I added an example Spark Streaming application to kafka-storm-starter that demonstrates how to read from Kafka and write to Kafka, using Avro as the data format and Twitter Bijection for handling the data serialization. In this post I will explain this Spark Streaming example in further detail and also shed some light on the current state of Kafka integration in Spark Streaming. All this with the disclaimer that this happens to be my first experiment with Spark Streaming.</blockquote>

]]></description>
<dc:subject>spark kafka realtime architecture queues avro bijection batch-processing</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jm/b:2ff12c1b1ca4/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:spark"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:kafka"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:realtime"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:architecture"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:queues"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:avro"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:bijection"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:batch-processing"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://sourceforge.net/projects/ccfreaks/files/papers/LeftRight/leftright-extended.pdf">
    <title>&quot;Left-Right: A Concurrency Control Technique with Wait-Free Population Oblivious Reads&quot; [pdf]</title>
    <dc:date>2014-09-17T14:29:55+00:00</dc:date>
    <link>http://sourceforge.net/projects/ccfreaks/files/papers/LeftRight/leftright-extended.pdf</link>
    <dc:creator>jm</dc:creator><description><![CDATA['In this paper, we describe a generic concurrency control technique with Blocking write operations and Wait-Free Population Oblivious read operations, which we named the Left-Right technique. It is of particular interest for real-time applications with dedicated Reader threads, due to its wait-free property that gives strong latency guarantees and, in addition, there is no need for automatic Garbage Collection.
The Left-Right pattern can be applied to any data structure, allowing concurrent access to it similarly to a Reader-Writer lock, but in a non-blocking manner for reads. We present several variations of the Left-Right technique, with different versioning mechanisms and state machines. In addition, we constructed an optimistic approach that can reduce synchronization for reads.'

See also http://concurrencyfreaks.blogspot.ie/2013/12/left-right-concurrency-control.html for java implementation code.]]></description>
<dc:subject>left-right concurrency multithreading wait-free blocking realtime gc latency reader-writer locking synchronization java</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jm/b:71e20ba2b8b1/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:left-right"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:concurrency"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:multithreading"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:wait-free"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:blocking"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:realtime"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:gc"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:latency"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:reader-writer"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:locking"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:synchronization"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:java"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://blog.twitter.com/2014/fighting-spam-with-botmaker">
    <title>Fighting spam with BotMaker</title>
    <dc:date>2014-08-22T15:13:35+00:00</dc:date>
    <link>https://blog.twitter.com/2014/fighting-spam-with-botmaker</link>
    <dc:creator>jm</dc:creator><description><![CDATA[Some vague details of the antispam system in use at Twitter.

<blockquote>The main challenges in supporting this type of system are evaluating rules with low enough latency that they can run on the write path for Twitter’s main features (i.e., Tweets, Retweets, favorites, follows and messages), supporting computationally intense machine learning based rules, and providing Twitter engineers with the ability to modify and create new rules instantaneously.</blockquote>

]]></description>
<dc:subject>spam realtime scaling twitter anti-spam botmaker rules</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jm/b:608530e05a81/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:spam"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:realtime"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:scaling"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:twitter"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:anti-spam"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:botmaker"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:rules"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.slideshare.net/tantrieuf31/real-time-analytics-with-netty-storm-kafka">
    <title>Real time analytics with Netty, Storm, Kafka</title>
    <dc:date>2014-08-09T11:32:45+00:00</dc:date>
    <link>http://www.slideshare.net/tantrieuf31/real-time-analytics-with-netty-storm-kafka</link>
    <dc:creator>jm</dc:creator><description><![CDATA[Arch of a fairly typical Kafka/Storm realtime ad-tracking setup, from eClick/mc2ads, via Trustin Lee]]></description>
<dc:subject>via:trustinlee kafka storm netty architecture ad-tracking ads realtime</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jm/b:fe33709a254d/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:via:trustinlee"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:kafka"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:storm"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:netty"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:architecture"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:ad-tracking"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:ads"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:realtime"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://news.ycombinator.com/item?id=7711974">
    <title>Why Disqus made the Python-&gt;Go switchover</title>
    <dc:date>2014-05-08T13:34:52+00:00</dc:date>
    <link>https://news.ycombinator.com/item?id=7711974</link>
    <dc:creator>jm</dc:creator><description><![CDATA[for their realtime component, from the horse's mouth:

<blockquote>at higher contention, the CPU was choking everything. Switching over to Go removed that contention for us, which was the primary issue that we were seeing.</blockquote>

]]></description>
<dc:subject>python languages concurrency go threading gevent scalability disqus realtime hn</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jm/b:7735324765d8/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:python"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:languages"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:concurrency"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:go"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:threading"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:gevent"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:scalability"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:disqus"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:realtime"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:hn"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://speakerdeck.com/pyconslides/scaling-realtime-at-disqus-by-adam-hitchcock">
    <title>Scaling Realtime at DISQUS</title>
    <dc:date>2014-04-30T10:57:02+00:00</dc:date>
    <link>https://speakerdeck.com/pyconslides/scaling-realtime-at-disqus-by-adam-hitchcock</link>
    <dc:creator>jm</dc:creator><description><![CDATA[Disqus' realtime architecture -- nginx PushStream module doing the heavy lifting, basically.  See https://gist.github.com/dctrwatson/0b3b52050254e273ff11 for the production nginx configs they use.  I am very impressed that push-stream has grown to be so solid; it's a great way to deal with push from the sounds of it.

http://blog.disqus.com/post/51155103801/trying-out-this-go-thing now notes that some of the realtime backends are in Go.

https://speakerdeck.com/dctrwatson/c1m-and-nginx ("C1M and Nginx") is a more up to date presentation.  It notes that PushStream supports "EventSource, WebSocket, Long Polling, and forever iframe".  More sysctls and nginx tuning in that prez.]]></description>
<dc:subject>sysctl nginx tuning go disqus realtime push eventsource websockets long-polling iframe python</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jm/b:92ccc8b3f3ef/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:sysctl"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:nginx"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:tuning"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:go"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:disqus"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:realtime"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:push"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:eventsource"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:websockets"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:long-polling"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:iframe"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:python"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://yahooeng.tumblr.com/post/65453012905/introducing-samoa-an-open-source-platform-for-mining">
    <title>SAMOA, an open source platform for mining big data streams</title>
    <dc:date>2013-11-25T11:10:35+00:00</dc:date>
    <link>http://yahooeng.tumblr.com/post/65453012905/introducing-samoa-an-open-source-platform-for-mining</link>
    <dc:creator>jm</dc:creator><description><![CDATA[Yahoo!'s streaming machine learning platform, built on Storm, implementing:

<blockquote>
As a library, SAMOA contains state-of-the-art implementations of algorithms for distributed machine learning on streams. The first alpha release allows classification and clustering.  For classification, we implemented a Vertical Hoeffding Tree (VHT), a distributed streaming version of decision trees tailored for sparse data (e.g., text). For clustering, we included a distributed algorithm based on CluStream. The library also includes meta-algorithms such as bagging.
</blockquote>]]></description>
<dc:subject>storm streaming big-data realtime samoa yahoo machine-learning ml decision-trees clustering bagging classification</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jm/b:785df99d0cee/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:storm"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:streaming"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:big-data"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:realtime"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:samoa"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:yahoo"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:machine-learning"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:ml"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:decision-trees"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:clustering"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:bagging"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:classification"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://reverbrain.com/grape/">
    <title>Grape</title>
    <dc:date>2013-11-20T12:36:47+00:00</dc:date>
    <link>http://reverbrain.com/grape/</link>
    <dc:creator>jm</dc:creator><description><![CDATA[a realtime processing engine, built on a persistent queue and a set of workers.  'The main goal is data availability and persistency.  We created grape for those who cannot afford losing data'.  It does this by allowing infinite expansion of the pending queue in Elliptics, their Dynamo-like horizontally-scaled storage backend.]]></description>
<dc:subject>kafka queue queueing storage realtime fault-tolerance grape cep event-processing</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jm/b:269fc0b4ff60/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:kafka"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:queue"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:queueing"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:storage"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:realtime"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:fault-tolerance"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:grape"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:cep"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:event-processing"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.edn.com/design/automotive/4423428/Toyota-s-killer-firmware--Bad-design-and-its-consequences">
    <title>Toyota's killer firmware: Bad design and its consequences</title>
    <dc:date>2013-10-30T10:55:21+00:00</dc:date>
    <link>http://www.edn.com/design/automotive/4423428/Toyota-s-killer-firmware--Bad-design-and-its-consequences</link>
    <dc:creator>jm</dc:creator><description><![CDATA[This is exactly what you do NOT want to read about embedded systems controlling acceleration in your car:

<blockquote>
The Camry electronic throttle control system code was found to have 11,000 global variables. Barr described the code as “spaghetti.” Using the Cyclomatic Complexity metric, 67 functions were rated untestable (meaning they scored more than 50). The throttle angle function scored more than 100 (unmaintainable).
Toyota loosely followed the widely adopted MISRA-C coding rules but Barr’s group found 80,000 rule violations. Toyota's own internal standards make use of only 11 MISRA-C rules, and five of those were violated in the actual code. MISRA-C:1998, in effect when the code was originally written, has 93 required and 34 advisory rules. Toyota nailed six of them.  Barr also discovered inadequate and untracked peer code reviews and the absence of any bug-tracking system at Toyota.
</blockquote>

On top of this, there was no error-correcting RAM in use; stack-killing recursive code; a quoted 94% stack usage; risks of unintentional RTOS task shutdown; buffer overflows; unsafe casting; race conditions; unchecked error code return values; and a trivial watchdog timer check.  Crappy, unsafe coding.]]></description>
<dc:subject>firmware horror embedded-systems toyota camry safety acceleration misra-c coding code-verification spaghetti-code cyclomatic-complexity realtime rtos c code-reviews bug-tracking quality</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jm/b:acba21cb4f78/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:firmware"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:horror"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:embedded-systems"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:toyota"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:camry"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:safety"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:acceleration"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:misra-c"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:coding"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:code-verification"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:spaghetti-code"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:cyclomatic-complexity"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:realtime"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:rtos"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:c"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:code-reviews"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:bug-tracking"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:quality"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.slideshare.net/ashleywbrown/storm-at-spiderio-london-storm-meetup-20130618">
    <title>Storm at spider.io - London Storm Meetup 2013-06-18</title>
    <dc:date>2013-10-29T11:18:21+00:00</dc:date>
    <link>http://www.slideshare.net/ashleywbrown/storm-at-spiderio-london-storm-meetup-20130618</link>
    <dc:creator>jm</dc:creator><description><![CDATA[Not just a Storm success story.  Interesting slides indicating where a startup *stopped* using Storm as realtime wasn't useful to their customers]]></description>
<dc:subject>storm realtime hadoop cascading python cep spider.io anti-spam events architecture distcomp low-latency slides rabbitmq</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jm/b:3fcd16536c76/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:storm"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:realtime"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:hadoop"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:cascading"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:python"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:cep"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:spider.io"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:anti-spam"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:events"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:architecture"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:distcomp"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:low-latency"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:slides"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:rabbitmq"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://www.facebook.com/notes/facebook-engineering/wormhole-pubsub-system-moving-data-through-space-and-time/10151504075843920">
    <title>Facebook announce Wormhole</title>
    <dc:date>2013-06-26T09:38:27+00:00</dc:date>
    <link>https://www.facebook.com/notes/facebook-engineering/wormhole-pubsub-system-moving-data-through-space-and-time/10151504075843920</link>
    <dc:creator>jm</dc:creator><description><![CDATA[<blockquote>Over the last couple of years, we have built and deployed a reliable publish-subscribe system called Wormhole. Wormhole has become a critical part of Facebook's software infrastructure. At a high level, Wormhole propagates changes issued in one system to all systems that need to reflect those changes – within and across data centers. </blockquote>

Facebook's Kafka-alike, basically, although with some additional low-latency guarantees.  FB appear to be using it for multi-region and multi-AZ replication. Proprietary.]]></description>
<dc:subject>pub-sub scalability facebook realtime low-latency multi-region replication multi-az wormhole</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jm/b:c16235547374/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:pub-sub"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:scalability"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:facebook"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:realtime"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:low-latency"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:multi-region"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:replication"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:multi-az"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:wormhole"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.infoq.com/interviews/ennis-events">
    <title>Darach Ennis on CEP, Stream Processing, Messaging, OOP vs Functional Architecture</title>
    <dc:date>2013-05-14T21:03:27+00:00</dc:date>
    <link>http://www.infoq.com/interviews/ennis-events</link>
    <dc:creator>jm</dc:creator><description><![CDATA[good interview -- lots of food for thought!]]></description>
<dc:subject>darach-ennis stream-processing messaging architecture qcon interviews erlang cep realtime rx comet events</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jm/b:262333000223/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:darach-ennis"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:stream-processing"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:messaging"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:architecture"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:qcon"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:interviews"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:erlang"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:cep"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:realtime"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:rx"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:comet"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:events"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://developers.google.com/drive/realtime/">
    <title>Google Drive SDK</title>
    <dc:date>2013-03-20T12:09:20+00:00</dc:date>
    <link>https://developers.google.com/drive/realtime/</link>
    <dc:creator>jm</dc:creator><description><![CDATA[realtime collaboration API.  nifty!  but can it collaborate on a per-app shared doc, or does it require that the app user auth to Google and access their own docs?]]></description>
<dc:subject>collaboration api realtime google javascript</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jm/b:69a2edc2ffba/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:collaboration"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:api"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:realtime"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:google"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:javascript"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://engineering.twitter.com/2012/08/trident-high-level-abstraction-for.html">
    <title>Trident: a high-level abstraction for realtime computation</title>
    <dc:date>2012-10-08T11:06:01+00:00</dc:date>
    <link>http://engineering.twitter.com/2012/08/trident-high-level-abstraction-for.html</link>
    <dc:creator>jm</dc:creator><description><![CDATA[built on Storm:

<blockquote>
Trident is a new high-level abstraction for doing realtime computing on top of Twitter Storm, available in Storm 0.8.0. It allows you to seamlessly mix high throughput (millions of messages per second), stateful stream processing with low latency distributed querying. If you're familiar with high level batch processing tools like Pig or Cascading, the concepts of Trident will be very familiar - Trident has joins, aggregations, grouping, functions, and filters. In addition to these, Trident adds primitives for doing stateful, incremental processing on top of any database or persistence store. Trident has consistent, exactly-once semantics, so it is easy to reason about Trident topologies.
</blockquote>
]]></description>
<dc:subject>distributed realtime twitter storm trident distcomp stream-processing low-latency nathan-marz</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jm/b:b7481a5f029d/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:distributed"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:realtime"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:twitter"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:storm"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:trident"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:distcomp"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:stream-processing"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:low-latency"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:nathan-marz"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://nathanmarz.com/blog/how-to-beat-the-cap-theorem.html">
    <title>How to beat the CAP theorem</title>
    <dc:date>2011-10-22T22:46:38+00:00</dc:date>
    <link>http://nathanmarz.com/blog/how-to-beat-the-cap-theorem.html</link>
    <dc:creator>jm</dc:creator><description><![CDATA[Nathan "Storm" Marz on building a dual realtime/batch stack. This lines up with something I've been building in work, so I'm happy ;)]]></description>
<dc:subject>nathan-marz realtime batch hadoop storm big-data cap</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jm/b:20004ab62fdd/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:nathan-marz"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:realtime"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:batch"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:hadoop"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:storm"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:big-data"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:cap"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.slideshare.net/nathanmarz/storm-distributed-and-faulttolerant-realtime-computation">
    <title>Storm: distributed and fault-tolerant realtime computation</title>
    <dc:date>2011-09-20T21:57:37+00:00</dc:date>
    <link>http://www.slideshare.net/nathanmarz/storm-distributed-and-faulttolerant-realtime-computation</link>
    <dc:creator>jm</dc:creator><description><![CDATA[intro slideshow to this really nifty-looking distcomp platform]]></description>
<dc:subject>distcomp distributed realtime storm slides twitter</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jm/b:9652fbca2b57/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:distcomp"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:distributed"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:realtime"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:storm"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:slides"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:twitter"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://github.com/nathanmarz/storm/wiki/Rationale">
    <title>Storm</title>
    <dc:date>2011-09-20T21:04:42+00:00</dc:date>
    <link>https://github.com/nathanmarz/storm/wiki/Rationale</link>
    <dc:creator>jm</dc:creator><description><![CDATA['The past decade has seen a revolution in data processing. MapReduce, Hadoop, and related technologies have made it possible to store and process data at scales previously unthinkable. Unfortunately, these data processing technologies are not realtime systems, nor are they meant to be. There's no hack that will turn Hadoop into a realtime system; realtime data processing has a fundamentally different set of requirements than batch processing.

However, realtime data processing at massive scale is becoming more and more of a requirement for businesses. The lack of a "Hadoop of realtime" has become the biggest hole in the data processing ecosystem.  Storm fills that hole.'

]]></description>
<dc:subject>data scaling twitter realtime scalability storm queueing</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jm/b:0781f3875d18/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:data"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:scaling"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:twitter"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:realtime"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:scalability"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:storm"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:queueing"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.slideshare.net/nathanmarz/the-secrets-of-building-realtime-big-data-systems">
    <title>The Secrets of Building Realtime Big Data Systems</title>
    <dc:date>2011-05-23T23:13:12+00:00</dc:date>
    <link>http://www.slideshare.net/nathanmarz/the-secrets-of-building-realtime-big-data-systems</link>
    <dc:creator>jm</dc:creator><description><![CDATA[great slides, via HN.  recommends a canonical Hadoop long-term store and a quick, realtime, separate datastore for "not yet processed by Hadoop" data]]></description>
<dc:subject>hadoop big-data data scalability datamining realtime slides presentations</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jm/b:cddf36f77523/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:hadoop"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:big-data"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:data"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:scalability"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:datamining"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:realtime"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:slides"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:presentations"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://russ.garrett.co.uk/2010/01/10/semi-realtime-satellite-desktop-backgrounds/">
    <title>Semi-Realtime Satellite Desktop Backgrounds</title>
    <dc:date>2010-01-12T20:59:02+00:00</dc:date>
    <link>http://russ.garrett.co.uk/2010/01/10/semi-realtime-satellite-desktop-backgrounds/</link>
    <dc:creator>jm</dc:creator><description><![CDATA[Russ Garrett with another set of near-realtime desktop weather imagery (cf. http://taint.org/xplanet/ )]]></description>
<dc:subject>weather desktop image satellite realtime backgrounds</dc:subject>
<dc:identifier>https://pinboard.in/u:jm/b:b56bda56c3a1/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:weather"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:desktop"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:image"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:satellite"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:realtime"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:backgrounds"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://dashes.com/anil/2009/07/the-pushbutton-web-realtime-becomes-real.html">
    <title>The Pushbutton Web: Realtime Becomes Real</title>
    <dc:date>2009-07-24T15:48:47+00:00</dc:date>
    <link>http://dashes.com/anil/2009/07/the-pushbutton-web-realtime-becomes-real.html</link>
    <dc:creator>jm</dc:creator><description><![CDATA[good wrap-up from Anil Dash on "the new push"]]></description>
<dc:subject>http-push http feeds atom ping standards messaging pubsubhubbub pubsub async comet realtime web</dc:subject>
<dc:identifier>https://pinboard.in/u:jm/b:470f67ac4575/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:http-push"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:http"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:feeds"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:atom"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:ping"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:standards"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:messaging"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:pubsubhubbub"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:pubsub"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:async"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:comet"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:realtime"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:web"/>
</rdf:Bag></taxo:topics>
</item>
</rdf:RDF>