<?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://kichik.com/2022/08/31/lessons-learned-from-1tb-dynamodb-import/"/>
	<rdf:li rdf:resource="https://trino.io/blog/2022/05/05/tardigrade-launch.html"/>
	<rdf:li rdf:resource="https://medium.com/bigdatarepublic/a-review-of-netflixs-metaflow-65c6956e168d"/>
	<rdf:li rdf:resource="https://argoproj.github.io/argo"/>
	<rdf:li rdf:resource="https://codeascraft.com/2018/11/14/boundary-layer%e2%80%89-declarative-airflow-workflows/"/>
	<rdf:li rdf:resource="https://mapzen.com/blog/terrain-tiles-on-aws-batch/"/>
	<rdf:li rdf:resource="https://www.nextflow.io/"/>
	<rdf:li rdf:resource="http://docs.aws.amazon.com/AmazonECS/latest/developerguide/scheduled_tasks.html"/>
	<rdf:li rdf:resource="https://www.youtube.com/watch?v=dgaoqOZlvEA&amp;feature=youtu.be"/>
	<rdf:li rdf:resource="https://gtoonstra.github.io/etl-with-airflow/index.html"/>
	<rdf:li rdf:resource="http://blogs.aws.amazon.com/bigdata/post/Tx578UTQUV7LRP/Submitting-User-Applications-with-spark-submit"/>
	<rdf:li rdf:resource="https://medium.com/@foundev/real-time-analytics-with-spark-streaming-and-cassandra-2f90d03342f7"/>
	<rdf:li rdf:resource="https://beta.oreilly.com/ideas/the-world-beyond-batch-streaming-101"/>
	<rdf:li rdf:resource="http://blog.acolyer.org/2015/06/19/discretized-streams-fault-tolerant-stream-computing-at-scale/"/>
	<rdf:li rdf:resource="http://nerds.airbnb.com/airflow/"/>
	<rdf:li rdf:resource="http://www.slideshare.net/databricks/strata-sj-everyday-im-shuffling-tips-for-writing-better-spark-programs"/>
	<rdf:li rdf:resource="http://www.frankmcsherry.org/graph/scalability/cost/2015/01/15/COST.html"/>
	<rdf:li rdf:resource="http://databricks.com/blog/2014/12/19/announcing-spark-1-2.html"/>
	<rdf:li rdf:resource="http://databricks.com/blog/2014/10/10/spark-breaks-previous-large-scale-sort-record.html"/>
	<rdf:li rdf:resource="http://radar.oreilly.com/2014/07/questioning-the-lambda-architecture.html"/>
	<rdf:li rdf:resource="https://blog.twitter.com/2014/tsar-a-timeseries-aggregator"/>
	<rdf:li rdf:resource="http://www.slideshare.net/cpwatson/cpn302-yourlinuxamioptimizationandperformance"/>
	<rdf:li rdf:resource="http://highscalability.com/blog/2013/1/7/analyzing-billions-of-credit-card-transactions-and-serving-l.html"/>
	<rdf:li rdf:resource="http://nathanmarz.com/blog/how-to-beat-the-cap-theorem.html"/>
      </rdf:Seq>
    </items>
  </channel><item rdf:about="https://kichik.com/2022/08/31/lessons-learned-from-1tb-dynamodb-import/">
    <title>Lessons Learned from 1TB DynamoDB Import</title>
    <dc:date>2023-10-24T17:07:10+00:00</dc:date>
    <link>https://kichik.com/2022/08/31/lessons-learned-from-1tb-dynamodb-import/</link>
    <dc:creator>jm</dc:creator><description><![CDATA[good advice for large scale DynamoDB usage. better yet is to avoid having to do big imports in the first place of course :)]]></description>
<dc:subject>backfills dynamodb batch scaling aws</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jm/b:b117711019c1/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:backfills"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:dynamodb"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:batch"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:scaling"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:aws"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://trino.io/blog/2022/05/05/tardigrade-launch.html">
    <title>Trino | Project Tardigrade delivers ETL at Trino speeds to early users</title>
    <dc:date>2022-05-10T09:26:37+00:00</dc:date>
    <link>https://trino.io/blog/2022/05/05/tardigrade-launch.html</link>
    <dc:creator>jm</dc:creator><description><![CDATA[This looks fantastic -- Trino (nee Presto) adds some significant improvements for long-running and heavyweight query support.

<blockquote>When your long-running queries experience a failure, they don’t have to start from scratch.
When queries require more memory than currently available in the cluster they are still able to succeed.
When multiple queries are submitted concurrently they are able to share resources in a fair way, and make steady progress.</blockquote>

]]></description>
<dc:subject>trino presto sql storage querying etl batch scheduling</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jm/b:890646400b31/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:trino"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:presto"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:sql"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:storage"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:querying"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:etl"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:batch"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:scheduling"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://medium.com/bigdatarepublic/a-review-of-netflixs-metaflow-65c6956e168d">
    <title>A Review of Netflix’s Metaflow</title>
    <dc:date>2020-01-22T12:14:32+00:00</dc:date>
    <link>https://medium.com/bigdatarepublic/a-review-of-netflixs-metaflow-65c6956e168d</link>
    <dc:creator>jm</dc:creator><description><![CDATA[Metaflow looks nice, and used by $work's data scientists]]></description>
<dc:subject>metaflow data-science data batch architecture</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jm/b:98bc54a96c89/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:metaflow"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:data-science"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:data"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:batch"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:architecture"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://argoproj.github.io/argo">
    <title>Argo Workflows &amp; Pipelines</title>
    <dc:date>2019-02-28T10:44:37+00:00</dc:date>
    <link>https://argoproj.github.io/argo</link>
    <dc:creator>jm</dc:creator><description><![CDATA[Nice new workflow system built on Kubernetes and Docker]]></description>
<dc:subject>k8s kubernetes docker containers workflow pipelines architecture batch nightly-jobs ops</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jm/b:0cd7daacad31/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:k8s"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:kubernetes"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:docker"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:containers"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:workflow"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:pipelines"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:architecture"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:batch"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:nightly-jobs"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:ops"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://codeascraft.com/2018/11/14/boundary-layer%e2%80%89-declarative-airflow-workflows/">
    <title>boundary-layer</title>
    <dc:date>2018-11-27T20:38:15+00:00</dc:date>
    <link>https://codeascraft.com/2018/11/14/boundary-layer%e2%80%89-declarative-airflow-workflows/</link>
    <dc:creator>jm</dc:creator><description><![CDATA[Declarative Airflow Workflows in YAML, from Etsy]]></description>
<dc:subject>airflow python batch cron etl</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jm/b:5d4305c3f31a/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:airflow"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:python"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:batch"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:cron"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:etl"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://mapzen.com/blog/terrain-tiles-on-aws-batch/">
    <title>Using AWS Batch to Generate Mapzen Terrain Tiles · Mapzen</title>
    <dc:date>2017-12-05T22:09:37+00:00</dc:date>
    <link>https://mapzen.com/blog/terrain-tiles-on-aws-batch/</link>
    <dc:creator>jm</dc:creator><description><![CDATA[<blockquote>Using this setup on AWS Batch, we are able to generate more than 3.75 million tiles per minute and render the entire world in less than a week! These pre-rendered tiles get stored in S3 and are ready to use by anyone through the AWS Public Dataset or through Mapzen’s Terrain Tiles API.</blockquote>

]]></description>
<dc:subject>mapzen mapping tiles batch aws s3 lambda docker</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jm/b:a932f8829a8e/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:mapzen"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:mapping"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:tiles"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:batch"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:aws"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:s3"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:lambda"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:docker"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://www.nextflow.io/">
    <title>Nextflow - A DSL for parallel and scalable computational pipelines</title>
    <dc:date>2017-08-08T22:06:18+00:00</dc:date>
    <link>https://www.nextflow.io/</link>
    <dc:creator>jm</dc:creator><description><![CDATA[<blockquote>Data-driven computational pipelines

Nextflow enables scalable and reproducible scientific workflows using software containers. It allows the adaptation of pipelines written in the most common scripting languages.

Its fluent DSL simplifies the implementation and the deployment of complex parallel and reactive workflows on clouds and clusters.
</blockquote>

GPLv3 licensed, open source]]></description>
<dc:subject>computation workflows pipelines batch docker ops open-source</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jm/b:52d4c861f8a6/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:computation"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:workflows"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:pipelines"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:batch"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:docker"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:ops"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:open-source"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://docs.aws.amazon.com/AmazonECS/latest/developerguide/scheduled_tasks.html">
    <title>Scheduled Tasks (cron) - Amazon EC2 Container Service</title>
    <dc:date>2017-07-11T10:19:34+00:00</dc:date>
    <link>http://docs.aws.amazon.com/AmazonECS/latest/developerguide/scheduled_tasks.html</link>
    <dc:creator>jm</dc:creator><description><![CDATA[ECS now does cron jobs.  But where does AWS Batch fit in?  confusing]]></description>
<dc:subject>aws batch ecs cron scheduling recurrence ops</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jm/b:59ea65c27ff1/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:aws"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:batch"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:ecs"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:cron"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:scheduling"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:recurrence"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:ops"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://www.youtube.com/watch?v=dgaoqOZlvEA&amp;feature=youtu.be">
    <title>Best practices with Airflow</title>
    <dc:date>2016-10-19T10:22:04+00:00</dc:date>
    <link>https://www.youtube.com/watch?v=dgaoqOZlvEA&amp;feature=youtu.be</link>
    <dc:creator>jm</dc:creator><description><![CDATA[interesting presentation describing how to architect Airflow ETL setups; see also https://gtoonstra.github.io/etl-with-airflow/principles.html]]></description>
<dc:subject>etl airflow batch architecture systems ops</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jm/b:89b7e8acd127/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:etl"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:airflow"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:batch"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:architecture"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:systems"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:ops"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://gtoonstra.github.io/etl-with-airflow/index.html">
    <title>ETL best practices with Airflow</title>
    <dc:date>2016-10-17T09:46:07+00:00</dc:date>
    <link>https://gtoonstra.github.io/etl-with-airflow/index.html</link>
    <dc:creator>jm</dc:creator><description><![CDATA[good advice on how to ETL]]></description>
<dc:subject>etl airflow documentation best-practices batch architecture</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jm/b:2c8c42ae1e66/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:etl"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:airflow"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:documentation"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:best-practices"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:batch"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:architecture"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://blogs.aws.amazon.com/bigdata/post/Tx578UTQUV7LRP/Submitting-User-Applications-with-spark-submit">
    <title>Submitting User Applications with spark-submit - AWS Big Data Blog</title>
    <dc:date>2016-02-09T11:15:31+00:00</dc:date>
    <link>http://blogs.aws.amazon.com/bigdata/post/Tx578UTQUV7LRP/Submitting-User-Applications-with-spark-submit</link>
    <dc:creator>jm</dc:creator><description><![CDATA[looks reasonably usable, although EMR's crappy UI is still an issue]]></description>
<dc:subject>emr big-data spark hadoop yarn map-reduce batch</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jm/b:1a28e3a538b2/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:emr"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:big-data"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:spark"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:hadoop"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:yarn"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:map-reduce"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:batch"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://medium.com/@foundev/real-time-analytics-with-spark-streaming-and-cassandra-2f90d03342f7">
    <title>Real Time Analytics With Spark Streaming and Cassandra</title>
    <dc:date>2015-09-03T20:58:52+00:00</dc:date>
    <link>https://medium.com/@foundev/real-time-analytics-with-spark-streaming-and-cassandra-2f90d03342f7</link>
    <dc:creator>jm</dc:creator><description><![CDATA[...and Kafka
]]></description>
<dc:subject>spark-streaming kafka analytics cassandra architecture data batch</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jm/b:b0d85df5ec49/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:spark-streaming"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:kafka"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:analytics"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:cassandra"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:architecture"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:data"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:batch"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://beta.oreilly.com/ideas/the-world-beyond-batch-streaming-101">
    <title>The world beyond batch: Streaming 101 - O'Reilly Media</title>
    <dc:date>2015-08-17T14:09:05+00:00</dc:date>
    <link>https://beta.oreilly.com/ideas/the-world-beyond-batch-streaming-101</link>
    <dc:creator>jm</dc:creator><description><![CDATA[<blockquote>To summarize, in this post I’ve:

Clarified terminology, specifically narrowing the definition of “streaming” to apply to execution engines only, while using more descriptive terms like unbounded data and approximate/speculative results for distinct concepts often categorized under the “streaming” umbrella.

Assessed the relative capabilities of well-designed batch and streaming systems, positing that streaming is in fact a strict superset of batch, and that notions like the Lambda Architecture, which are predicated on streaming being inferior to batch, are destined for retirement as streaming systems mature.

Proposed two high-level concepts necessary for streaming systems to both catch up to and ultimately surpass batch, those being correctness and tools for reasoning about time, respectively.

Established the important differences between event time and processing time, characterized the difficulties those differences impose when analyzing data in the context of when they occurred, and proposed a shift in approach away from notions of completeness and toward simply adapting to changes in data over time.

Looked at the major data processing approaches in common use today for bounded and unbounded data, via both batch and streaming engines, roughly categorizing the unbounded approaches into: time-agnostic, approximation, windowing by processing time, and windowing by event time.</blockquote>

]]></description>
<dc:subject>streaming batch big-data lambda-architecture dataflow event-processing cep millwheel data data-processing</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jm/b:ef8048836663/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:streaming"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:batch"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:big-data"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:lambda-architecture"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:dataflow"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:event-processing"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:cep"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:millwheel"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:data"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:data-processing"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://blog.acolyer.org/2015/06/19/discretized-streams-fault-tolerant-stream-computing-at-scale/">
    <title>Discretized Streams: Fault Tolerant Stream Computing at Scale</title>
    <dc:date>2015-06-19T07:47:04+00:00</dc:date>
    <link>http://blog.acolyer.org/2015/06/19/discretized-streams-fault-tolerant-stream-computing-at-scale/</link>
    <dc:creator>jm</dc:creator><description><![CDATA[The paper describing the innards of Spark Streaming and its RDD-based recomputation algorithm:

<blockquote>we use a data structure called Resilient Distributed Datasets (RDDs), which keeps data in memory and can recover it without replication by tracking the lineage graph of operations that were used to build it. With RDDs, we show that we can attain sub-second end-to-end latencies. We believe that this is sufficient for many real-world big data applications, where the timescale of the events tracked (e.g., trends in social media) is much higher.</blockquote>

]]></description>
<dc:subject>rdd spark streaming fault-tolerance batch distcomp papers big-data scalability</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jm/b:561d8372a2de/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:rdd"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:spark"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:streaming"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:fault-tolerance"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:batch"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:distcomp"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:papers"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:big-data"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:scalability"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://nerds.airbnb.com/airflow/">
    <title>Airflow</title>
    <dc:date>2015-06-05T09:53:57+00:00</dc:date>
    <link>http://nerds.airbnb.com/airflow/</link>
    <dc:creator>jm</dc:creator><description><![CDATA[Airbnb's workflow management system; works off a DAG defined in Python code (ugh).  Nice UI though, but I think Pinboard's take is neater]]></description>
<dc:subject>airbnb open-source python workflow jobs cron scheduling batch</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jm/b:b89f8e9c803f/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:airbnb"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:open-source"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:python"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:workflow"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:jobs"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:cron"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:scheduling"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:batch"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.slideshare.net/databricks/strata-sj-everyday-im-shuffling-tips-for-writing-better-spark-programs">
    <title>Everyday I'm Shuffling - Tips for Writing Better Spark Programs [slides]</title>
    <dc:date>2015-02-23T21:54:41+00:00</dc:date>
    <link>http://www.slideshare.net/databricks/strata-sj-everyday-im-shuffling-tips-for-writing-better-spark-programs</link>
    <dc:creator>jm</dc:creator><description><![CDATA[Two Spark experts from Databricks provide some good tips]]></description>
<dc:subject>spark performance batch ops tips slides emr</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jm/b:aec80aa94d61/</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:performance"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:batch"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:ops"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:tips"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:slides"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:emr"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.frankmcsherry.org/graph/scalability/cost/2015/01/15/COST.html">
    <title>Are you better off running your big-data batch system off your laptop?</title>
    <dc:date>2015-01-17T21:33:33+00:00</dc:date>
    <link>http://www.frankmcsherry.org/graph/scalability/cost/2015/01/15/COST.html</link>
    <dc:creator>jm</dc:creator><description><![CDATA[Heh, nice trolling.<blockquote>Here are two helpful guidelines (for largely disjoint populations):

If you are going to use a big data system for yourself, see if it is faster than your laptop.
If you are going to build a big data system for others, see that it is faster than my laptop. [...]

We think everyone should have to do this, because it leads to better systems and better research.</blockquote>

]]></description>
<dc:subject>graph coding hadoop spark giraph graph-processing hardware scalability big-data batch algorithms pagerank</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jm/b:229db78fb862/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:graph"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:coding"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:hadoop"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:spark"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:giraph"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:graph-processing"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:hardware"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:scalability"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:big-data"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:batch"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:algorithms"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:pagerank"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://databricks.com/blog/2014/12/19/announcing-spark-1-2.html">
    <title>Spark 1.2 released</title>
    <dc:date>2014-12-22T14:14:17+00:00</dc:date>
    <link>http://databricks.com/blog/2014/12/19/announcing-spark-1-2.html</link>
    <dc:creator>jm</dc:creator><description><![CDATA[This is the version with the superfast petabyte-sort record:<blockquote>Spark 1.2 includes several cross-cutting optimizations focused on performance for large scale workloads. Two new features Databricks developed for our world record petabyte sort with Spark are turned on by default in Spark 1.2. The first is a re-architected network transfer subsystem that exploits Netty 4’s zero-copy IO and off heap buffer management. The second is Spark’s sort based shuffle implementation, which we’ve now made the default after significant testing in Spark 1.1. Together, we’ve seen these features give as much as 5X performance improvement for workloads with very large shuffles.</blockquote>

]]></description>
<dc:subject>spark sorting hadoop map-reduce batch databricks apache netty</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jm/b:6d93115441ec/</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:sorting"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:hadoop"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:map-reduce"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:batch"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:databricks"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:apache"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:netty"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://databricks.com/blog/2014/10/10/spark-breaks-previous-large-scale-sort-record.html">
    <title>Spark Breaks Previous Large-Scale Sort Record – Databricks</title>
    <dc:date>2014-10-10T20:33:57+00:00</dc:date>
    <link>http://databricks.com/blog/2014/10/10/spark-breaks-previous-large-scale-sort-record.html</link>
    <dc:creator>jm</dc:creator><description><![CDATA[Massive improvement over plain old Hadoop.  This blog post goes into really solid techie reasons why, including:

<blockquote>First and foremost, in Spark 1.1 we introduced a new shuffle implementation called sort-based shuffle (SPARK-2045). The previous Spark shuffle implementation was hash-based that required maintaining P (the number of reduce partitions) concurrent buffers in memory. In sort-based shuffle, at any given point only a single buffer is required. This has led to substantial memory overhead reduction during shuffle and can support workloads with hundreds of thousands of tasks in a single stage (our PB sort used 250,000 tasks).</blockquote>

Also, use of Timsort, an external shuffle service to offload from the JVM, Netty, and EC2 SR-IOV.]]></description>
<dc:subject>spark hadoop map-reduce batch parallel sr-iov benchmarks performance netty shuffle algorithms sort-based-shuffle timsort</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jm/b:c675a1f7b48b/</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:hadoop"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:map-reduce"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:batch"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:parallel"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:sr-iov"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:benchmarks"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:performance"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:netty"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:shuffle"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:algorithms"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:sort-based-shuffle"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:timsort"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://radar.oreilly.com/2014/07/questioning-the-lambda-architecture.html">
    <title>Questioning the Lambda Architecture</title>
    <dc:date>2014-07-03T17:07:11+00:00</dc:date>
    <link>http://radar.oreilly.com/2014/07/questioning-the-lambda-architecture.html</link>
    <dc:creator>jm</dc:creator><description><![CDATA[Jay Kreps (Kafka, Samza) with a thought-provoking post on the batch/stream-processing dichotomy]]></description>
<dc:subject>jay-kreps toread architecture data stream-processing batch hadoop storm lambda-architecture</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jm/b:a8ed8296bab9/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:jay-kreps"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:toread"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:architecture"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:data"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:stream-processing"/>
	<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:lambda-architecture"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://blog.twitter.com/2014/tsar-a-timeseries-aggregator">
    <title>Twitter's TSAR</title>
    <dc:date>2014-06-30T10:47:02+00:00</dc:date>
    <link>https://blog.twitter.com/2014/tsar-a-timeseries-aggregator</link>
    <dc:creator>jm</dc:creator><description><![CDATA[TSAR = "Time Series AggregatoR".  Twitter's new event processor-style architecture for internal metrics.  It's notable that now Twitter and Google are both apparently moving towards this idea of a model of code which is designed to run equally in realtime streaming and batch modes (Summingbird, Millwheel, Flume).]]></description>
<dc:subject>analytics architecture twitter tsar aggregation event-processing metrics streaming hadoop batch</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jm/b:663be2fcb029/</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:tsar"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:aggregation"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:event-processing"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:metrics"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:streaming"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:hadoop"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:batch"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.slideshare.net/cpwatson/cpn302-yourlinuxamioptimizationandperformance">
    <title>Netflix: Your Linux AMI: optimization and performance [slides]</title>
    <dc:date>2013-12-21T20:50:48+00:00</dc:date>
    <link>http://www.slideshare.net/cpwatson/cpn302-yourlinuxamioptimizationandperformance</link>
    <dc:creator>jm</dc:creator><description><![CDATA[a fantastic bunch of low-level kernel tweaks and tunables which Netflix have found useful in production to maximise productivity of their fleet.  Interesting use of SCHED_BATCH process scheduler class for batch processes, in particular.  Also, great docs on their experience with perf and SystemTap.  Perf really looks like a tool I need to get to grips with...]]></description>
<dc:subject>netflix aws tuning ami perf systemtap tunables sched_batch batch hadoop optimization performance</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jm/b:5c1292b5cc15/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:netflix"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:aws"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:tuning"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:ami"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:perf"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:systemtap"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:tunables"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:sched_batch"/>
	<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:optimization"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:performance"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://highscalability.com/blog/2013/1/7/analyzing-billions-of-credit-card-transactions-and-serving-l.html">
    <title>High Scalability - Analyzing billions of credit card transactions and serving low-latency insights in the cloud</title>
    <dc:date>2013-02-07T11:49:20+00:00</dc:date>
    <link>http://highscalability.com/blog/2013/1/7/analyzing-billions-of-credit-card-transactions-and-serving-l.html</link>
    <dc:creator>jm</dc:creator><description><![CDATA[Hadoop, a batch-generated read-only Voldemort cluster, and an intriguing optimal-storage histogram bucketing algorithm:

<blockquote>The optimal histogram is computed using a random-restart hill climbing approximated algorithm.
The algorithm has been shown very fast and accurate: we achieved 99% accuracy compared to an exact dynamic algorithm, with a speed increase of one factor.  [...] The amount of information to serve in Voldemort for one year of BBVA's credit card transactions on Spain is 270 GB. The whole processing flow would run in 11 hours on a cluster of 24 "m1.large" instances. The whole infrastructure, including the EC2 instances needed to serve the resulting data would cost approximately $3500/month.
</blockquote>
]]></description>
<dc:subject>scalability scaling voldemort hadoop batch algorithms histograms statistics bucketing percentiles</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jm/b:8012838d5d72/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:scalability"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:scaling"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:voldemort"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:hadoop"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:batch"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:algorithms"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:histograms"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:statistics"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:bucketing"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:percentiles"/>
</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>
</rdf:RDF>