incubator-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Henry Saputra <henry.sapu...@gmail.com>
Subject Re: [PROPOSAL] Samza Proposal
Date Wed, 31 Jul 2013 22:15:12 GMT
NP

Good luck and congrats

- Henry

On Wednesday, July 31, 2013, Chris Riccomini wrote:

> Hey Guys,
>
> Jakob (the project Champion) is in the process of getting all of the
> resources requested in our proposal (JIRA, Hudson, webspace, etc).
>
> As soon as we have webspace allocated, we'll put the Samza site up, which
> has all of these docs on it. Henry, as you said, I'll follow up with this
> thread when they're up.
>
> Cheers,
> Chris
>
>
> On Wed, Jul 31, 2013 at 2:04 PM, Henry Saputra <henry.saputra@gmail.com<javascript:;>
> >wrote:
>
> > Well, usually VOTE is conducted after discussion had calmed down. Looks
> > like this time the VOTE starts even though there were some question about
> > the proposal.
> >
> > Would be great to actually add links to the comparisons in the thread
> even
> > though the VOTE had concluded.
> >
> > - Henry
> >
> >
> > On Wed, Jul 31, 2013 at 1:29 PM, Phillip Rhodes
> > <motley.crue.fan@gmail.com>wrote:
> >
> > > Same here.  Not that it matters as far as admission to the incubator
> > > (that vote is over now anyway), but I think a lot of people (including
> > > potential users of Samza) would like to see more about how it compares
> > > & contrasts with other stream oriented systems.
> > >
> > >
> > > Phil
> > > This message optimized for indexing by NSA PRISM
> > >
> > >
> > > On Fri, Jul 26, 2013 at 8:27 PM, Alex Karasulu <akarasulu@apache.org>
> > > wrote:
> > > > +1
> > > >
> > > > I would love to see the "documents comparing and contrasting Samza
> with
> > > > MUPD8 and Storm."
> > > >
> > > >
> > > > On Sat, Jul 27, 2013 at 2:53 AM, Enis Söztutar <enis@apache.org>
> > wrote:
> > > >
> > > >> +1 on incubation.
> > > >>
> > > >> Enis
> > > >>
> > > >>
> > > >> On Tue, Jul 23, 2013 at 7:17 PM, Chris Riccomini
> > > >> <criccomini.aux@gmail.com>wrote:
> > > >>
> > > >> > Hey Henry and Debo,
> > > >> >
> > > >> > Thanks for calling this out. Samza's feature set includes:
> > > >> >
> > > >> >    - *Simpe API:* Unlike most low-level messaging system APIs,
> Samza
> > > >> >    provides a very simple call-back based "process message" API
> that
> > > >> > should be
> > > >> >    familiar to anyone that's used Map/Reduce.
> > > >> >    - *Managed state:* Samza manages snapshotting and restoration
> of
> > a
> > > >> >    stream processor's state. Samza will restore a stream
> processor's
> > > >> state
> > > >> > to
> > > >> >    a snapshot consistent with the processor's last read messages
> > when
> > > the
> > > >> >    processor is restarted.
> > > >> >    - *Fault tolerance:* Samza will work with YARN to restart
your
> > > stream
> > > >> >    processor if there is a machine or processor failure.
> > > >> >    - Durability: Samza uses Kafka to guarantee that no messages
> will
> > > ever
> > > >> >    be lost.
> > > >> >    - *Scalability:* Samza is partitioned and distributed at every
> > > level.
> > > >> >    Kafka provides ordered, partitioned, replayable, fault-tolerant
> > > >> streams.
> > > >> >    YARN provides a distributed environment for Samza containers
to
> > run
> > > >> in.
> > > >> >    - *Pluggable:* Though Samza works out of the box with Kafka
and
> > > YARN,
> > > >> >    Samza provides a pluggable API that lets you run Samza with
> other
> > > >> > messaging
> > > >> >    systems and execution environments.
> > > >> >    - *Processor isolation:* Samza works with Apache YARN, which
> > > supports
> > > >> >    processor security through Hadoop's security model, and
> resource
> > > >> > isolation
> > > >> >    through Linux CGroups.
> > > >> >
> > > >> > Some of these feature are available in S4, and some are not.
The
> > same
> > > >> holds
> > > >> > true for Storm.
> > > >> >
> > > >> > The open source stream processing systems that are available
are
> > > actually
> > > >> > quite young, and no single system offers a c

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message