Mailing-List: contact user-help@flink.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@flink.apache.org
MIME-Version: 1.0
In-Reply-To: <1478928438323-10050.post@n4.nabble.com>
References: <CA+X8dm-LgZhHGTK3pm0FXoHYNn_kQb--erjSixXXSKJfUHZqpQ@mail.gmail.com>
 <1478928438323-10050.post@n4.nabble.com>
From: Manish Shukla <manishukla1409@gmail.com>
Date: Sun, 13 Nov 2016 20:27:51 +0530
Message-ID: <CA+X8dm9V5s6PDOLB7RsZ_un=ih1iNThY30iopcjOcd8mq9h5iw@mail.gmail.com>
Subject: Re: Apache Flink Introduction Guide
To: user@flink.apache.org
Content-Type: multipart/alternative; boundary=001a114e68a081ae9305412ff2e3
archived-at: Sun, 13 Nov 2016 14:57:56 -0000

--001a114e68a081ae9305412ff2e3
Content-Type: text/plain; charset=UTF-8

Dear Anchit,

Thanks for the feedback, i am developing another article for streaming,
will include all the mentioned topics and mail here for the feedback again.

On Sat, Nov 12, 2016 at 10:57 AM, Anchit Jatana <
development.anchit@gmail.com> wrote:

> Hi Manish,
>
> Appreciate the way you presented Apache Flink. While it's like an 'Intro'
> to
> beginners, I would really encourage you to highlight/present some of the
> groundbreaking features that flink offers towards stream processing like -
>
> -> Explicit handling of time with it's notion of 'Event time' + 'Expressive
> and flexible windowing capabilities'
>
> -> State management + Fault tolerance through it's light-weight
> checkpointing/snapshotting mechanism
>
> -> Performance - in terms of low latency, throughput and back-pressure
> handling + comparative benchmarks with other engines in market.
>
> Since, any person who reads the blog should not just take the text as a
> 'Hello World' to 'another new' technology in town but take it seriously as
> to how this is better and how it beats the contemporary processing engines
> so that the reader understands how important it is for him to delve deeper
> into the topic and expand his knowledge about Flink which is going to be
> the
> next most adopted engine in industry.
>
> Regards,
> Anchit
>
>
>
>
> --
> View this message in context: http://apache-flink-user-
> mailing-list-archive.2336050.n4.nabble.com/Apache-Flink-
> Introduction-Guide-tp10041p10050.html
> Sent from the Apache Flink User Mailing List archive. mailing list archive
> at Nabble.com.
>

--001a114e68a081ae9305412ff2e3
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Dear Anchit,<div><br></div><div>Thanks for the feedback, i=
 am developing another article for streaming, will include all the mentione=
d topics and mail here for the feedback again.</div></div><div class=3D"gma=
il_extra"><br><div class=3D"gmail_quote">On Sat, Nov 12, 2016 at 10:57 AM, =
Anchit Jatana <span dir=3D"ltr">&lt;<a href=3D"mailto:development.anchit@gm=
ail.com" target=3D"_blank">development.anchit@gmail.com</a>&gt;</span> wrot=
e:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-l=
eft:1px #ccc solid;padding-left:1ex">Hi Manish,<br>
<br>
Appreciate the way you presented Apache Flink. While it&#39;s like an &#39;=
Intro&#39; to<br>
beginners, I would really encourage you to highlight/present some of the<br=
>
groundbreaking features that flink offers towards stream processing like -<=
br>
<br>
-&gt; Explicit handling of time with it&#39;s notion of &#39;Event time&#39=
; + &#39;Expressive<br>
and flexible windowing capabilities&#39;<br>
<br>
-&gt; State management + Fault tolerance through it&#39;s light-weight<br>
checkpointing/snapshotting mechanism<br>
<br>
-&gt; Performance - in terms of low latency, throughput and back-pressure<b=
r>
handling + comparative benchmarks with other engines in market.<br>
<br>
Since, any person who reads the blog should not just take the text as a<br>
&#39;Hello World&#39; to &#39;another new&#39; technology in town but take =
it seriously as<br>
to how this is better and how it beats the contemporary processing engines<=
br>
so that the reader understands how important it is for him to delve deeper<=
br>
into the topic and expand his knowledge about Flink which is going to be th=
e<br>
next most adopted engine in industry.<br>
<br>
Regards,<br>
Anchit<br>
<br>
<br>
<br>
<br>
--<br>
View this message in context: <a href=3D"http://apache-flink-user-mailing-l=
ist-archive.2336050.n4.nabble.com/Apache-Flink-Introduction-Guide-tp10041p1=
0050.html" rel=3D"noreferrer" target=3D"_blank">http://apache-flink-user-<w=
br>mailing-list-archive.2336050.<wbr>n4.nabble.com/Apache-Flink-<wbr>Introd=
uction-Guide-<wbr>tp10041p10050.html</a><br>
Sent from the Apache Flink User Mailing List archive. mailing list archive =
at Nabble.com.<br>
</blockquote></div><br></div>

--001a114e68a081ae9305412ff2e3--