This is an automated email from the ASF dual-hosted git repository.
mergebot-role pushed a commit to branch asf-site
in repository https://gitbox.apache.org/repos/asf/beam-site.git
commit f0e45db368e3018bc32dd6ab81785f69eedd2e59
Author: Mergebot <merge...@apache.org>
AuthorDate: Wed Jan 24 11:04:53 2018 -0800
Prepare repository for deployment.
---
content/blog/2018/01/09/beam-a-look-back.html | 280 ++++++++++++++++++++++++
content/blog/index.html | 21 ++
content/feed.xml | 176 ++++++++++++---
content/images/blog/2017-look-back/timeline.png | Bin 0 -> 12454 bytes
content/index.html | 10 +-
5 files changed, 446 insertions(+), 41 deletions(-)
diff --git a/content/blog/2018/01/09/beam-a-look-back.html
b/content/blog/2018/01/09/beam-a-look-back.html
new file mode 100644
index 0000000..9aa0275
--- /dev/null
+++ b/content/blog/2018/01/09/beam-a-look-back.html
@@ -0,0 +1,280 @@
+<!DOCTYPE html>
+<html lang="en">
+ <head>
+ <meta charset="utf-8">
+ <meta http-equiv="X-UA-Compatible" content="IE=edge">
+ <meta name="viewport" content="width=device-width, initial-scale=1">
+ <title>Apache Beam: A Look Back at 2017</title>
+ <meta name="description" content="On January 10, 2017, Apache Beam got
promotedas a Top-Level Apache Software Foundation project. It was an important
milestonethat validated the value of the ...">
+ <link href="https://fonts.googleapis.com/css?family=Roboto:100,300,400";
rel="stylesheet">
+ <link rel="stylesheet" href="/css/site.css">
+ <script
src="https://ajax.googleapis.com/ajax/libs/jquery/2.2.0/jquery.min.js";></script>
+ <script src="/js/bootstrap.min.js"></script>
+ <script src="/js/language-switch.js"></script>
+ <script src="/js/fix-menu.js"></script>
+ <script src="/js/section-nav.js"></script>
+ <script src="/js/page-nav.js"></script>
+ <link rel="canonical"
href="https://beam.apache.org/blog/2018/01/09/beam-a-look-back.html";
data-proofer-ignore>
+ <link rel="shortcut icon" type="image/x-icon" href="/images/favicon.ico">
+ <link rel="alternate" type="application/rss+xml" title="Apache Beam"
href="https://beam.apache.org/feed.xml";>
+ <script>
+
(function(i,s,o,g,r,a,m){i['GoogleAnalyticsObject']=r;i[r]=i[r]||function(){
+ (i[r].q=i[r].q||[]).push(arguments)},i[r].l=1*new
Date();a=s.createElement(o),
+
m=s.getElementsByTagName(o)[0];a.async=1;a.src=g;m.parentNode.insertBefore(a,m)
+
})(window,document,'script','//www.google-analytics.com/analytics.js','ga');
+ ga('create', 'UA-73650088-1', 'auto');
+ ga('send', 'pageview');
+ </script>
+</head>
+
+ <body class="body ">
+ <nav class="header navbar navbar-fixed-top">
+ <div class="navbar-header">
+ <button type="button" class="navbar-toggle" aria-expanded="false"
aria-controls="navbar">
+ <span class="sr-only">Toggle navigation</span>
+ <span class="icon-bar"></span>
+ <span class="icon-bar"></span>
+ <span class="icon-bar"></span>
+ </button>
+
+ <a href="/" class="navbar-brand" >
+ <img alt="Brand" style="height: 25px"
src="/images/beam_logo_navbar.png">
+ </a>
+ </div>
+
+ <div class="navbar-mask closed"></div>
+
+ <div id="navbar" class="navbar-container closed">
+ <ul class="nav navbar-nav">
+ <li>
+ <a href="/get-started/beam-overview/">Get Started</a>
+ </li>
+ <li>
+ <a href="/documentation/">Documentation</a>
+ </li>
+ <li>
+ <a href="/documentation/sdks/java/">SDKS</a>
+ </li>
+ <li>
+ <a href="/documentation/runners/capability-matrix/">RUNNERS</a>
+ </li>
+ <li>
+ <a href="/contribute/">Contribute</a>
+ </li>
+ <li><a href="/blog">Blog</a></li>
+ </ul>
+ <ul class="nav navbar-nav navbar-right">
+ <li class="dropdown">
+ <a href="#" class="dropdown-toggle" data-toggle="dropdown"
role="button" aria-haspopup="true" aria-expanded="false"><img
src="https://www.apache.org/foundation/press/kit/feather_small.png"; alt="Apache
Logo" style="height:20px;"><span class="caret"></span></a>
+ <ul class="dropdown-menu dropdown-menu-right">
+ <li><a href="http://www.apache.org/";>ASF Homepage</a></li>
+ <li><a href="http://www.apache.org/licenses/";>License</a></li>
+ <li><a href="http://www.apache.org/security/";>Security</a></li>
+ <li><a
href="http://www.apache.org/foundation/thanks.html";>Thanks</a></li>
+ <li><a
href="http://www.apache.org/foundation/sponsorship.html";>Sponsorship</a></li>
+ <li><a
href="https://www.apache.org/foundation/policies/conduct";>Code of
Conduct</a></li>
+ </ul>
+ </li>
+ </ul>
+ </div>
+</nav>
+
+ <div class="body__contained">
+
+
+<article class="post" itemscope itemtype="http://schema.org/BlogPosting";>
+
+ <header class="post-header">
+ <h1 class="post-title" itemprop="name headline">Apache Beam: A Look Back
at 2017</h1>
+ <p class="post-meta"><time datetime="2018-01-09T00:00:01-08:00"
itemprop="datePublished">Jan 9, 2018</time> • Anand Iyer & Jean-Baptiste
Onofré [<a href="https://twitter.com/jbonofre";>@jbonofre</a>]
+</p>
+ </header>
+
+ <div class="post-content" itemprop="articleBody">
+ <p>On January 10, 2017, Apache Beam got <a
href="/blog/2017/01/10/beam-graduates.html">promoted</a>
+as a Top-Level Apache Software Foundation project. It was an important
milestone
+that validated the value of the project, legitimacy of its community, and
+heralded its growing adoption. In the past year, Apache Beam has been on a
+phenomenal growth trajectory, with significant growth in its community and
+feature set. Let us walk you through some of the notable achievements.</p>
+
+<!--more-->
+
+<h2 id="use-cases">Use cases</h2>
+
+<p>First, lets take a glimpse at how Beam was used in 2017. Apache Beam being a
+unified framework for batch and stream processing, enables a very wide spectrum
+of diverse use cases. Here are some use cases that exemplify the versatility of
+Beam.</p>
+
+<p><img class="center-block" src="/images/blog/2017-look-back/timeline.png"
alt="Use Cases" width="600" /></p>
+
+<h2 id="community-growth">Community growth</h2>
+
+<p>In 2017, Apache Beam had 174 contributors worldwide, from many different
+organizations. As an Apache project, we are proud to count 18 PMC members and
+31 committers. The community had 7 releases in 2017, each bringing a rich set
of
+new features and fixes.</p>
+
+<p>The most obvious and encouraging sign of the growth of Apache Beam’s
community,
+and validation of its core value proposition of portability, is the addition of
+significant new <a href="/documentation/runners/capability-matrix/">runners</a>
+(i.e. execution engines). We entered 2017 with Apache Flink, Apache Spark 1.x,
+Google Cloud Dataflow, Apache Apex, and Apache Gearpump. In 2017, the following
+new and updated runners were developed:</p>
+
+<ul>
+ <li>Apache Spark 2.x update</li>
+ <li><a
href="https://www.ibm.com/blogs/bluemix/2017/10/streaming-analytics-updates-ibm-streams-runner-apache-beam-2-0/";>IBM
Streams runner</a></li>
+ <li>MapReduce runner</li>
+ <li><a href="http://jstorm.io/";>JStorm runner</a></li>
+</ul>
+
+<p>In addition to runners, Beam added new IO connectors, some notable ones
being
+the Cassandra, MQTT, AMQP, HBase/HCatalog, JDBC, Solr, Tika, Redis, and
+ElasticSearch connectors. Beam’s IO connectors make it possible to read from or
+write to data sources/sinks even when they are not natively supported by the
+underlying execution engine. Beam also provides fully pluggable filesystem
+support, allowing us to support and extend our coverage to HDFS, S3, Azure
+Storage, and Google Storage. We continue to add new IO connectors and
+filesystems to extend the Beam use cases.</p>
+
+<p>A particularly telling sign of the maturity of an open source community is
when
+it is able to collaborate with multiple other open source communities, and
+mutually improve the state of the art. Over the past few months, the Beam,
+Calcite, and Flink communities have come together to define a robust <a
href="https://docs.google.com/document/d/1wrla8mF_mmq-NW9sdJHYVgMyZsgCmHumJJ5f5WUzTiM/edit";>spec</a>
+for Streaming SQL, with engineers from over four organizations contributing to
+it. If, like us, you are excited by the prospect of improving the state of
+streaming SQL, please join us!</p>
+
+<p>In addition to SQL, new XML and JSON based declarative DSLs are also in
PoC.</p>
+
+<h2 id="continued-innovation">Continued innovation</h2>
+
+<p>Innovation is important to the success on any open source project, and Beam
has
+a rich history of bringing innovative new ideas to the open source community.
+Apache Beam was the first to introduce some seminal concepts in the world of
+big-data processing:</p>
+
+<ul>
+ <li>Unified batch and streaming SDK that enables users to author big-data
jobs
+without having to learn multiple disparate SDKs/APIs.</li>
+ <li>Cross-Engine Portability: Giving enterprises the confidence that
workloads
+authored today will not have to be re-written when open source engines become
+outdated and are supplanted by newer ones.</li>
+ <li><a
href="https://www.oreilly.com/ideas/the-world-beyond-batch-streaming-101";>Semantics</a>
+essential for reasoning about unbounded unordered data, and achieving
+consistent and correct output from a streaming job.</li>
+</ul>
+
+<p>In 2017, the pace of innovation continued. The following capabilities were
+introduced:</p>
+
+<ul>
+ <li>Cross-Language Portability framework, and a <a
href="https://golang.org/";>Go</a> SDK
+developed with it.</li>
+ <li>Dynamically Shardable IO (SplittableDoFn)</li>
+ <li>Support for schemas in PCollection, allowing us to extend the runner
+capabilities.</li>
+ <li>Extensions addressing new use cases such as machine learning, and new
data
+formats.</li>
+</ul>
+
+<h2 id="areas-of-improvement">Areas of improvement</h2>
+
+<p>Any retrospective view of a project is incomplete without an honest
assessment
+of areas of improvement. Two aspects stand out:</p>
+
+<ul>
+ <li>Helping runners showcase their individual strengths. After all,
portability
+does not imply homogeneity. Different runners have different areas in which
+they excel, and we need to do a better job of helping them highlight their
+strengths.</li>
+ <li>Based on the previous point, helping customers make a more informed
decision
+when they select a runner or migrate from one to another.</li>
+</ul>
+
+<p>In 2018, we aim to take proactive steps to improve the above aspects.</p>
+
+<h2 id="ethos-of-the-project-and-its-community">Ethos of the project and its
community</h2>
+
+<p>The world of batch and stream big-data processing today is reminiscent of
the
+<a href="https://en.wikipedia.org/wiki/Tower_of_Babel";>Tower of Babel</a>
parable: a
+slowdown of progress because different communities spoke different languages.
+Similarly, today there are multiple disparate big-data SDKs/APIs, each with
+their own distinct terminology to describe similar concepts. The side effect is
+user confusion and slower adoption.</p>
+
+<p>The Apache Beam project aims to provide an industry standard portable SDK
that
+will:</p>
+
+<ul>
+ <li>Benefit users by providing <strong><em>innovation with
stability</em></strong>: The separation of
+SDK and engine enables healthy competition between runners, without requiring
+users to constantly learn new SDKs/APIs and rewrite their workloads to
+benefit from new innovation.</li>
+ <li>Benefit big-data engines by <strong><em>growing the pie for
everyone</em></strong>: Making it
+easier for users to author, maintain, upgrade and migrate their big-data
+workloads will lead to significant growth in the number of production
+big-data deployments.</li>
+</ul>
+
+
+ </div>
+
+</article>
+
+ </div>
+ <footer class="footer">
+ <div class="footer__contained">
+ <div class="footer__cols">
+ <div class="footer__cols__col">
+ <div class="footer__cols__col__logo">
+ <img src="/images/beam_logo_circle.svg" class="footer__logo"
alt="Beam logo">
+ </div>
+ <div class="footer__cols__col__logo">
+ <img src="/images/apache_logo_circle.svg" class="footer__logo"
alt="Apache logo">
+ </div>
+ </div>
+ <div class="footer__cols__col footer__cols__col--md">
+ <div class="footer__cols__col__title">Start</div>
+ <div class="footer__cols__col__link"><a
href="/get-started/beam-overview/">Overview</a></div>
+ <div class="footer__cols__col__link"><a
href="/get-started/quickstart-java/">Quickstart (Java)</a></div>
+ <div class="footer__cols__col__link"><a
href="/get-started/quickstart-py/">Quickstart (Python)</a></div>
+ <div class="footer__cols__col__link"><a
href="/get-started/downloads/">Downloads</a></div>
+ </div>
+ <div class="footer__cols__col footer__cols__col--md">
+ <div class="footer__cols__col__title">Docs</div>
+ <div class="footer__cols__col__link"><a
href="/documentation/programming-guide/">Concepts</a></div>
+ <div class="footer__cols__col__link"><a
href="/documentation/pipelines/design-your-pipeline/">Pipelines</a></div>
+ <div class="footer__cols__col__link"><a
href="/documentation/runners/capability-matrix/">Runners</a></div>
+ </div>
+ <div class="footer__cols__col footer__cols__col--md">
+ <div class="footer__cols__col__title">Community</div>
+ <div class="footer__cols__col__link"><a
href="/contribute/">Contribute</a></div>
+ <div class="footer__cols__col__link"><a
href="/contribute/team/">Team</a></div>
+ <div class="footer__cols__col__link"><a
href="/contribute/presentation-materials/">Media</a></div>
+ </div>
+ <div class="footer__cols__col footer__cols__col--md">
+ <div class="footer__cols__col__title">Resources</div>
+ <div class="footer__cols__col__link"><a href="/blog/">Blog</a></div>
+ <div class="footer__cols__col__link"><a
href="/get-started/support/">Support</a></div>
+ <div class="footer__cols__col__link"><a
href="https://github.com/apache/beam";>GitHub</a></div>
+ </div>
+ </div>
+ </div>
+ <div class="footer__bottom">
+ ©
+ <a href="http://www.apache.org";>The Apache Software Foundation</a>
+ | <a href="/privacy_policy">Privacy Policy</a>
+ | <a href="/feed.xml">RSS Feed</a>
+ <br><br>
+ Apache Beam, Apache, Beam, the Beam logo, and the Apache feather logo are
+ either registered trademarks or trademarks of The Apache Software
+ Foundation. All other products or name brands are trademarks of their
+ respective holders, including The Apache Software Foundation.
+ </div>
+</footer>
+
+ </body>
+</html>
diff --git a/content/blog/index.html b/content/blog/index.html
index 40deb97..a68c0ec 100644
--- a/content/blog/index.html
+++ b/content/blog/index.html
@@ -86,6 +86,27 @@
<p>This is the blog for the Apache Beam project. This blog contains news and
updates
for the project.</p>
+<h3
id="a-classpost-link-hrefblog20180109beam-a-look-backhtmlapache-beam-a-look-back-at-2017a"><a
class="post-link" href="/blog/2018/01/09/beam-a-look-back.html">Apache Beam: A
Look Back at 2017</a></h3>
+<p><i>Jan 9, 2018 • Anand Iyer & Jean-Baptiste Onofré [<a
href="https://twitter.com/jbonofre";>@jbonofre</a>]
+</i></p>
+
+<p>On January 10, 2017, Apache Beam got <a
href="/blog/2017/01/10/beam-graduates.html">promoted</a>
+as a Top-Level Apache Software Foundation project. It was an important
milestone
+that validated the value of the project, legitimacy of its community, and
+heralded its growing adoption. In the past year, Apache Beam has been on a
+phenomenal growth trajectory, with significant growth in its community and
+feature set. Let us walk you through some of the notable achievements.</p>
+
+<!-- Render a "read more" button if the post is longer than the excerpt -->
+
+<p>
+<a class="btn btn-default btn-sm"
href="/blog/2018/01/09/beam-a-look-back.html" role="button">
+Read more <span class="glyphicon glyphicon-menu-right"
aria-hidden="true"></span>
+</a>
+</p>
+
+<hr />
+
<h3
id="a-classpost-link-hrefblog20170828timely-processinghtmltimely-and-stateful-processing-with-apache-beama"><a
class="post-link" href="/blog/2017/08/28/timely-processing.html">Timely (and
Stateful) Processing with Apache Beam</a></h3>
<p><i>Aug 28, 2017 • Kenneth Knowles [<a
href="https://twitter.com/KennKnowles";>@KennKnowles</a>]
</i></p>
diff --git a/content/feed.xml b/content/feed.xml
index 08ae3ae..8e0966a 100644
--- a/content/feed.xml
+++ b/content/feed.xml
@@ -9,6 +9,146 @@
<generator>Jekyll v3.2.0</generator>
<item>
+ <title>Apache Beam: A Look Back at 2017</title>
+ <description><p>On January 10, 2017, Apache Beam got <a
href="/blog/2017/01/10/beam-graduates.html">promoted</a>
+as a Top-Level Apache Software Foundation project. It was an important
milestone
+that validated the value of the project, legitimacy of its community, and
+heralded its growing adoption. In the past year, Apache Beam has been on a
+phenomenal growth trajectory, with significant growth in its community and
+feature set. Let us walk you through some of the notable
achievements.</p>
+
+<!--more-->
+
+<h2 id="use-cases">Use cases</h2>
+
+<p>First, lets take a glimpse at how Beam was used in 2017. Apache Beam
being a
+unified framework for batch and stream processing, enables a very wide spectrum
+of diverse use cases. Here are some use cases that exemplify the versatility of
+Beam.</p>
+
+<p><img class="center-block"
src="/images/blog/2017-look-back/timeline.png" alt="Use
Cases" width="600" /></p>
+
+<h2 id="community-growth">Community growth</h2>
+
+<p>In 2017, Apache Beam had 174 contributors worldwide, from many
different
+organizations. As an Apache project, we are proud to count 18 PMC members and
+31 committers. The community had 7 releases in 2017, each bringing a rich set
of
+new features and fixes.</p>
+
+<p>The most obvious and encouraging sign of the growth of Apache Beam’s
community,
+and validation of its core value proposition of portability, is the addition of
+significant new <a
href="/documentation/runners/capability-matrix/">runners</a>
+(i.e. execution engines). We entered 2017 with Apache Flink, Apache Spark 1.x,
+Google Cloud Dataflow, Apache Apex, and Apache Gearpump. In 2017, the following
+new and updated runners were developed:</p>
+
+<ul>
+ <li>Apache Spark 2.x update</li>
+ <li><a
href="https://www.ibm.com/blogs/bluemix/2017/10/streaming-analytics-updates-ibm-streams-runner-apache-beam-2-0/">IBM
Streams runner</a></li>
+ <li>MapReduce runner</li>
+ <li><a href="http://jstorm.io/">JStorm
runner</a></li>
+</ul>
+
+<p>In addition to runners, Beam added new IO connectors, some notable
ones being
+the Cassandra, MQTT, AMQP, HBase/HCatalog, JDBC, Solr, Tika, Redis, and
+ElasticSearch connectors. Beam’s IO connectors make it possible to read from or
+write to data sources/sinks even when they are not natively supported by the
+underlying execution engine. Beam also provides fully pluggable filesystem
+support, allowing us to support and extend our coverage to HDFS, S3, Azure
+Storage, and Google Storage. We continue to add new IO connectors and
+filesystems to extend the Beam use cases.</p>
+
+<p>A particularly telling sign of the maturity of an open source
community is when
+it is able to collaborate with multiple other open source communities, and
+mutually improve the state of the art. Over the past few months, the Beam,
+Calcite, and Flink communities have come together to define a robust <a
href="https://docs.google.com/document/d/1wrla8mF_mmq-NW9sdJHYVgMyZsgCmHumJJ5f5WUzTiM/edit">spec</a>
+for Streaming SQL, with engineers from over four organizations contributing to
+it. If, like us, you are excited by the prospect of improving the state of
+streaming SQL, please join us!</p>
+
+<p>In addition to SQL, new XML and JSON based declarative DSLs are also
in PoC.</p>
+
+<h2 id="continued-innovation">Continued innovation</h2>
+
+<p>Innovation is important to the success on any open source project,
and Beam has
+a rich history of bringing innovative new ideas to the open source community.
+Apache Beam was the first to introduce some seminal concepts in the world of
+big-data processing:</p>
+
+<ul>
+ <li>Unified batch and streaming SDK that enables users to author
big-data jobs
+without having to learn multiple disparate SDKs/APIs.</li>
+ <li>Cross-Engine Portability: Giving enterprises the confidence that
workloads
+authored today will not have to be re-written when open source engines become
+outdated and are supplanted by newer ones.</li>
+ <li><a
href="https://www.oreilly.com/ideas/the-world-beyond-batch-streaming-101">Semantics</a>
+essential for reasoning about unbounded unordered data, and achieving
+consistent and correct output from a streaming job.</li>
+</ul>
+
+<p>In 2017, the pace of innovation continued. The following capabilities
were
+introduced:</p>
+
+<ul>
+ <li>Cross-Language Portability framework, and a <a
href="https://golang.org/">Go</a> SDK
+developed with it.</li>
+ <li>Dynamically Shardable IO (SplittableDoFn)</li>
+ <li>Support for schemas in PCollection, allowing us to extend the
runner
+capabilities.</li>
+ <li>Extensions addressing new use cases such as machine learning, and
new data
+formats.</li>
+</ul>
+
+<h2 id="areas-of-improvement">Areas of improvement</h2>
+
+<p>Any retrospective view of a project is incomplete without an honest
assessment
+of areas of improvement. Two aspects stand out:</p>
+
+<ul>
+ <li>Helping runners showcase their individual strengths. After all,
portability
+does not imply homogeneity. Different runners have different areas in which
+they excel, and we need to do a better job of helping them highlight their
+strengths.</li>
+ <li>Based on the previous point, helping customers make a more
informed decision
+when they select a runner or migrate from one to another.</li>
+</ul>
+
+<p>In 2018, we aim to take proactive steps to improve the above
aspects.</p>
+
+<h2 id="ethos-of-the-project-and-its-community">Ethos of the
project and its community</h2>
+
+<p>The world of batch and stream big-data processing today is
reminiscent of the
+<a href="https://en.wikipedia.org/wiki/Tower_of_Babel">Tower
of Babel</a> parable: a
+slowdown of progress because different communities spoke different languages.
+Similarly, today there are multiple disparate big-data SDKs/APIs, each with
+their own distinct terminology to describe similar concepts. The side effect is
+user confusion and slower adoption.</p>
+
+<p>The Apache Beam project aims to provide an industry standard portable
SDK that
+will:</p>
+
+<ul>
+ <li>Benefit users by providing <strong><em>innovation with
stability</em></strong>: The separation of
+SDK and engine enables healthy competition between runners, without requiring
+users to constantly learn new SDKs/APIs and rewrite their workloads to
+benefit from new innovation.</li>
+ <li>Benefit big-data engines by <strong><em>growing the
pie for everyone</em></strong>: Making it
+easier for users to author, maintain, upgrade and migrate their big-data
+workloads will lead to significant growth in the number of production
+big-data deployments.</li>
+</ul>
+
+</description>
+ <pubDate>Tue, 09 Jan 2018 00:00:01 -0800</pubDate>
+
<link>https://beam.apache.org/blog/2018/01/09/beam-a-look-back.html</link>
+ <guid
isPermaLink="true">https://beam.apache.org/blog/2018/01/09/beam-a-look-back.html</guid>
+
+
+ <category>blog</category>
+
+ </item>
+
+ <item>
<title>Timely (and Stateful) Processing with Apache Beam</title>
<description><p>In a <a
href="/blog/2017/02/13/stateful-processing.html">prior blog
post</a>, I
@@ -2326,41 +2466,5 @@ Java SDK. If you have questions or comments, we’d love
to hear them on the
</item>
- <item>
- <title>Strata+Hadoop World and Beam</title>
- <description><p>Tyler Akidau and I gave a <a
href="http://conferences.oreilly.com/strata/hadoop-big-data-ny/public/schedule/detail/52129">three-hour
tutorial</a> on Apache Beam at Strata+Hadoop World 2016. We had a
plethora of help from our TAs: Kenn Knowles, Reuven Lax, Felipe Hoffa, Slava
Chernyak, and Jamie Grier. There were a total of 66 people that attended the
session.<!--more--></p>
-
-<p><img src="/images/blog/IMG_20160927_170956.jpg"
alt="Exercise time" /></p>
-
-<p>If you want to take a look at the tutorial materials, we’ve put them
up <a href="https://github.com/eljefe6a/beamexample">on
GitHub</a>. This includes the <a
href="https://github.com/eljefe6a/beamexample/blob/master/BeamTutorial/slides.pdf">actual
slides</a> as well as the <a
href="https://github.com/eljefe6a/beamexample/tree/master/BeamTutorial/src/main/java/org/apache/beam/examples/tutorial/game">exercises</a>
t [...]
-
-<p>I want to share some of takeaways I had about Beam during the
conference.</p>
-
-<p>The Data Engineers are looking to Beam as a way to <a
href="https://www.oreilly.com/ideas/future-proof-and-scale-proof-your-code">future-proof</a>,
meaning that code is portable between the various Big Data frameworks. In
fact, many of the attendees were still on Hadoop MapReduce and looking to
transition to a new framework. They’re realizing that continually rewriting
code isn’t the most productive approach.</p>
-
-<p>Data Scientists are really interested in using Beam. They interested
in having a single API for doing analysis instead of several different APIs. We
talked about Beam’s progress on the Python API. If you want to take a peek,
it’s being actively developed on a <a
href="https://github.com/apache/beam/tree/master/sdks/python">feature
branch</a>. As Beam matures, we’re looking to add other supported
languages.</p>
-
-<p>We heard <a
href="https://twitter.com/jessetanderson/status/781124173108305920">loud
and clear</a> from Beam users that great runner support is crucial to
adoption. We have great Apache Flink support. During the conference we had some
more volunteers offer their help on the Spark runner.</p>
-
-<p>On management and thought leader side, Beam went from “what’s Beam?”
at previous conferences to “I’m interested in Beam.” or “I’ve formed an
informed opinion on Beam.” at this conference. This is one of the metrics I
look for in early technology adoption.</p>
-
-<p><img src="/images/blog/IMG_20160927_170455.jpg"
alt="So much brainpower answering questions" /></p>
-
-<p>We rounded out the tutorial with live demonstrations of Beam running
on Apache Spark, Apache Flink, the local runner, and DataFlow runner. Then, we
brought in the big brainpower and had a Q and A session.</p>
-
-<p>If you’re attending a conference, we encourage you to look for a Beam
session. If you want to use these materials to give your own Beam talk or
tutorial, we’re happy to help you. In addition to this tutorial, we have <a
href="/contribute/presentation-materials/">other presentation
materials</a>. You can reach out to us on the <a
href="/get-started/support/">user mailing list</a>.</p>
-
-</description>
- <pubDate>Tue, 11 Oct 2016 10:00:00 -0700</pubDate>
-
<link>https://beam.apache.org/beam/update/2016/10/11/strata-hadoop-world-and-beam.html</link>
- <guid
isPermaLink="true">https://beam.apache.org/beam/update/2016/10/11/strata-hadoop-world-and-beam.html</guid>
-
-
- <category>beam</category>
-
- <category>update</category>
-
- </item>
-
</channel>
</rss>
diff --git a/content/images/blog/2017-look-back/timeline.png
b/content/images/blog/2017-look-back/timeline.png
new file mode 100644
index 0000000..0394cd8
Binary files /dev/null and b/content/images/blog/2017-look-back/timeline.png
differ
diff --git a/content/index.html b/content/index.html
index c57527c..4caeb7a 100644
--- a/content/index.html
+++ b/content/index.html
@@ -109,6 +109,11 @@
</div>
<div class="hero__blog__cards">
+ <a class="hero__blog__cards__card"
href="/blog/2018/01/09/beam-a-look-back.html">
+ <div class="hero__blog__cards__card__title">Apache Beam: A Look
Back at 2017</div>
+ <div class="hero__blog__cards__card__date">Jan 9, 2018</div>
+ </a>
+
<a class="hero__blog__cards__card"
href="/blog/2017/08/28/timely-processing.html">
<div class="hero__blog__cards__card__title">Timely (and
Stateful) Processing with Apache Beam</div>
<div class="hero__blog__cards__card__date">Aug 28, 2017</div>
@@ -119,11 +124,6 @@
<div class="hero__blog__cards__card__date">Aug 16, 2017</div>
</a>
- <a class="hero__blog__cards__card"
href="/blog/2017/05/17/beam-first-stable-release.html">
- <div class="hero__blog__cards__card__title">Apache Beam
publishes the first stable release</div>
- <div class="hero__blog__cards__card__date">May 17, 2017</div>
- </a>
-
</div>
</div>
</div>
--
To stop receiving notification emails like this one, please contact
mergebot-r...@apache.org.
![https://www.apache.org/foundation/press/kit/feather_small.png"](https://www.apache.org/foundation/press/kit/feather_small.png"){kind=link}