►
From YouTube: NYC* 2013 - "Volly"
Description
Speakers: Jeff Sigman & Sanjay Sharma of Volly
https://www.volly.com
B
B
So
this
is
sanjay,
he
said
his
laptop
is
the
ones
running
the
show,
so
I
won't
know
any,
and
there
was
lots
ability
for
the
technical
glitches.
I
worked
at
pitney
bowes
and
what
I'm
going
to
talk
to
you
about
is
a
solution
called
Bali,
which
is
our
answer
to
the
fact
that
we
know
the
mail
is
going
away.
Mail
is
going
down
and
we
know
that
everybody
wants
to
have
their
bills
and
statements,
and
things
like
that
delivered
digitally.
So
I
was
working
on
the
program
to
take
to
build
up
something
called
volley.
B
B
B
We
go
it's
a
secure
spam
free,
opt
in
a
digital
delivery
service
that
will
empower
customers
to
receive
you
receive
review.
You
I'm
sorry
received
you
organize
and
manage
all
house
that
accounts
statements
and
stuff
online
and
it
should
go,
but
it's
not
okay
and
it's
a
secure
digital
delivery
of
service
that
collects
various
statements,
and
things
like
that.
You
can
read
the
statements
there,
but
that's
a
big
blob
of
information.
It's
kind
of
a
hard
to
understand
the
whole
point
is
males
going
away.
B
How
do
I
get
my
important
stuff
online
and
not
through
email,
so
a
simpler
version
of
it
is
one
place
to
go
for
everything.
11
password
gets
you
into
everything,
your
bills,
your
statements,
your
bank,
account
all
that
information
is
stored
in
one
online
presence
and
then,
of
course,
how
do
you
have
all
this
information?
You
have
all
the
mail
stacking
up
on
life
on
your
desk.
If
you're
still
getting
mail,
what
do
I
do
with
it?
You
can
organize
it
in
volley
as
well.
B
It's
not
just
a
place
to
gather
information,
it's
a
place
where
you
can
tag
stuff
and
highlight
things
and
organize
it
for
you
for
your
taxes,
your
mortgage
statements
and
things
like
that
and,
of
course,
in
one
place,
all
your
bills
that
are
you're
getting
in
one
place.
You
can
organize
them
sift
through
them,
decide
what's
what's
important.
What's
not
all
one
again,
once
again
one
portal
one
place
and
then
of
course
you
can
set
your
alerts
to
get
information.
You
paid
your
bill,
you
didn't
pay
your
bill.
B
You
want
to
pay
this
bill
15
days
earlier
than
the
other
ones.
I
want
to
point
to
the
last
minute
to
pay
that
one.
So
there's
a
lot
of
customization,
you
can
do
that
you
can.
You
can
pay
all
your
bills
the
way
you're
trying
to
do
it
with
volley
and,
most
importantly,
is
the
security
aspect
of
a
volley
all
of
the
information
that
we
get
from
from
your
credit
card
holder,
Sears
income
tax,
whatever
you
want
a
store
in
bali,
gets
stored
securely
and
that's
a
very
important
prospect
for
volley.
B
B
B
That
we
had
to
get
through
in
order
to
develop
this
thing.
It's
a
consumer
base
web
portal.
The
pitney
bowes
company,
is
traditionally
very
working
at
the
b2b
space,
so
this
is
a
much
larger
piece
of
data
than
we
were
typically
working
on
and
we
own
store
all
the
key
documents
there
and
it's
got
to
be
permanent
storage.
Today,
if
you
go
on,
if
you
pick
a
bank
and
get
all
your
statements
stored
online
switch
banks,
guess
what
happens
all
your
bank
statements
can't
get
them
online
anymore.
B
B
We
have
to
make
sure
we're
taking
care
of
different
businesses
in
different
countries
in
the
u.s..
Bali
is
a
full-length
full
application.
We
do
the
portal,
we
do
the
whole
whole
nine
yards,
but
in
across
the
world
as
other
places
where
they
only
want
Valley
to
be
the
piping
underneath
it
as
a
service.
So
how
do
you
balance
the
needs
of
the
US,
where
we
want
a
full
solution
with
Australia
Post
or
the
places
like
that
where
they
just
want
to
have
the
piping
and
things
like
that,
and
do
it
all
efficiently
and
then.
B
Database
data
models
where
some
countries
have
rules,
since
you
have
to
store
all
the
information
in
the
country
in
their
databases
other
places,
let
you
store
whatever
you
want,
wherever
you
want
now,
the
places
we'd
rather
by
the
by
the
visa
storage,
rather
than
have
it
stored
ourselves
and
then,
of
course,
security,
a
big
concern
for
it.
So
how
do
we
build
that
tank
like
a
global
search
security
into
all
the
documents,
information
all
like
and
stuff
and
manage
it
across
countries
across
the
world
across
users?
B
B
Don't
care
about
any
of
this
kind
of
stuff
they
want
it
to
be
fast.
I
want
to
all
in
one
place
and
I
want
to
be
a
little
tag.
All
my
stuff,
that's
sort
of
the
core
proposition
to
the
consumer
behind
the
scenes.
They
want
to
know
any
of
that
kind
of
stuff
and
be
able
to
tag
stuff
so
that
I
can
say
this
is
for
my
taxes.
This
is
for
a
mortgage
if
I
want
to
refinance-
and
things
like
that.
B
So
then,
just
to
give
you
a
little
information
that
says
this
isn't.
This
is
not
just
a
small
little
pet
project
right,
2
billion
transaction
documents
will
be
delivered
in
the
US
through
a
digital
mailbox.
That's
a
research
that
was
done
and,
of
course,
there's.
The
bigger
mark
is
about
a
half
billion.
So
there's
a
lot
of
information.
B
B
What
the
consumer
proposition
is:
that's
people
logging
into
the
system
getting
all
the
information
pulling
their
bills
down
tagging
their
bills,
storing
away
their
wills
and
statements.
Things
like
that
at
the
bottom
of
the
diagram
is
the
people
that
really
make
the
system
run.
These
are
the
people
are
sending
you
your
mail
today,
they're
sending
your
credit
card
statements,
your
wireless
bills
and
all
that
kind
of
stuff.
Those
people
have
to
put
to
see
our
content
into
the
system
in
order
for
the
consumer
to
be
able
to
see
it
so
not.
B
And
then,
of
course,
there's
many
ways
that
we
designed
to
get
it
in
there,
whether
that's
through
it
something
called
a
secure
mail
gateway
or
a
hosted,
secure,
male
gay
gay
where
we
take
a
box
and
put
it
on
premises
and
then,
whether
we're
with
or
without
transformations,
we
built
an
SDK.
So
there's
a
couple
different
ways
that
we
had
the
support
of
getting
it
all
into
that
big
cluster
of
ollie.
So.
C
B
D
Chef,
so
those
are
the
challenges
that
around
two
and
a
half
years
ago,
Surya
sake.
Vb
volley
program
came
to
one
of
our
presentations
in
cloud
expo
right
here,
lil,
island
of
manhattan
and
we're
presenting
on
hadoop
in
the
club,
and
that's
where
we
heard
about
this
challenge
these
challenges
and
we
started
a
journey
and
that's
what
I
am
going
to
share
about
today,
the
journey
that
we
had
to
had
over
the
last
couple
of
years
in
building
volume.
D
So
I
work
for
him,
peters
technologies
and
we
basically
are
advisors,
architects
and
application,
builders,
the
visual
of
san
jose,
and
we
have
been
focusing
in
victor
of
the
last
34
years.
Of
course,
we
work
across
multiple
technologies.
We
are
vendor
agnostic
and
what
we
also
help
in
is
strategizing
big
data
architecture,
proof
of
concepts
and,
of
course,
helping
customers
in
the
applications
as
well.
So.
D
D
So
this
we
see
use
the
same
methodology
for
volley
as
well,
where
we
understood
all
the
technical
and
business
challenges,
of
course
understood
the
short-term
and
long-term
requirements,
and
what
we
use
is
something
called
our
evaluation
criteria
based
comparison
matrix
where
we
collect
all
the
technical
and
business
requirements
into
simple
matrix,
where
we
collate
all
the
evaluation
criteria,
and
then
you
can
use
a
simple
scoring
scoring
model
for
finding
the
right
solution.
Of
course,
that
involves
figuring
out
what
are
the
main
technology
tears
for?
D
D
D
So
you
see
some
representative
tier,
such
as
data
storage,
security
and
material,
so
of
course
build
a
custom
scoring
matrix
for
each
and
every
tier
and
for
data
store,
particularly,
we
had
to
come
up
with
a
solution
which
could
scale
to
petabytes
of
data,
of
course,
cloud
friendly,
and
we
further
divided
those
evaluation
criteria
to
certain
perspectives,
depending
on
the
end
user
profile,
group
or
team.
So,
basically,
you
have
different
teams
which
have
different
perspective
of
their
business
and
technical
requirements.
They
talk
about
operational
perspective,
development
team
perspective,
infractions
of
deployment
management
testing
as
well.
D
D
Architecture
where
you
have
different
components,
and
one
of
the
most
interesting
challenges
that
we
had
to
solve
was
a
builder
cloud
agnostic
solution.
So
eric
in
the
previous
discussion
was
talking
about.
How
do
we
move
how
we
might
become
interlock
without
the
clouds
and
molly
initially
did
not
have
very
good
experiences
with
multiple
cloud
vendors,
so
the
first
imperative
was
to
build
something
which
would
work
across
cloud
and
that's
where
we
had
to
build
this
cloud
orchestration
framework
and
this
tour
official
framework
basically
is
based
on
Jake
level.
C
D
Specific
loud
we
can
deploy
it
on
multiple
clouds
so
that
we
can
have
the
main
cluster
running
same
rack
space,
while
the
well,
the
standby
server
can
run
over.
The
Sun
sent
by
a
cluster
can
run
in
amazing,
be
proud
or
any
other
element
in
the
club.
Of
course,
we
have
support
for
improvised
infectious
deployment
as
well,
which
means
that
you
can,
on
the
fly,
has
a.
D
As
well
as
proud
as
and
when
required,
so
it
automates
the
tour
decision
framework
takes
your
textures
of
data
data
synchronization
other
things
as
well.
Of
course,
cassandra
is
the
data
store,
which
is
the
main,
a
main
storage
mechanism
behind
behind
the
volley.
So
there
were
certain
features
in
Cassandra.
Of
course
we
had
to
go
through
that
entire
POC
or
a
benchmark
face
to
prove
that
all
the
isolates
were
being
met,
so
Cassandra
beat
everybody
right
or
left.
D
As
far
as
read,
read
and
write
speeds
were
concerned,
we
are
talking
about
mysterio
center
support
and
around
two
years
ago,
datastax
Cassandra
was
the
only
one
which
had
that
support
and
that's
where
cassandra
was
a
very
basic,
logical,
logical
option
for
us.
We
are
also
having,
of
course,
a
service-oriented
architecture
based
on
our
java
g2
a
spring
based
framework
and
we
rabbitmq
as
a
messaging
break
backbone
with
tomcat
asda
main
server
for
security.
We
have
a
lot
of.
C
D
What
were
the
lessons
that
we
have
learned
for
the
past
two
years
or
so,
and
of
course,
Michael
will
come
in
and
explain
how
datastax
all
the
Cassandra
community
has
been
able
to
overcome
and
provide
some
of
the
features
now.
But
we
had
to
start
around
two
and
a
half
years
ago
and
had
to
fight
many
hard
metals
and
blunted
the
hard
way.
So,
regarding.
D
Development,
one
of
the
first
things
that
we
understood
was
to
create
a
high
level
up
fraction
layer
over
the
low-level
API
and,
of
course
this
was
required
because
we
had
us.
We
had
to
have
security
built
in
at
data
in
rest,
as
well
as
data
in
motion.
So
for
Cassandra
we
actually
used
this
high
level
API
layer
for
encapsulating
all
the
security
and
all
the
underlying
hsm
utter
security-based
interactions
to
ensure
that
all
the
documents
or
all
the
PII
or
PK
data
or
PCA
data
are
encrypted.
C
B
D
Explorer
for
the
Q
and
the
testing
team
for
for
the
photo
there
manual
testing-
and
this
is
a
podcast-
you
I,
of
course
it's
open
source.
We
also
open
source
product
called
thundera
k,
u
nder
a
which
is
an
ORM
which
basically
can
run
across
no
sequel
solutions
and,
of
course,
Cassandra
was
really
handy.
Given
that
we
were,
we
were
facing
the
challenges
with
heavy
batch
right
and,
of
course,
real-time
reads,
and
we
had
to
play
on
a
lot
with
the
consistency
model
and
the
cashew
model
and
the
cash
cash
in
model
as
well.
B
D
Of
course,
araucana
touched
upon
that
we're,
monitoring
and
management
needs
to
be
abstracted
and
you
should
have
it
controlled
as
early
as
possible.
So
we
use
a
high
breakage
Cubase
to
management
suite
where
we
could
utilize
Cassandra,
jmx,
based
monitoring
and,
of
course,
continuous
monitoring
of
Cassandra
really
helps
in
ensuring
that
you
do
not
get
into
to
bigger
problems
and.
D
D
Zing
him
until
backup
and
disaster
recovery
support
across
clouds,
as
I
mentioned
and
significantly
nothing
Cassandra
was
the
only
solution
which
could
provide
such
a
kind
of
flexibility
between
multiple
clouds
or
within
within
a
single.
Our
descent,
ellisville,
of
course,
are
talking
about
security
everywhere
that
I
in
race
anti-tank
motion,
so
whether
we
are
talking
about
to
iPad.
C
D
C
D
One
is
currently
running
on
at
aramark
cluster,
and
we
can
have
a
backup
running
on
rackspace
autumn
is
an
episode.
Has
it
been
required?
Of
course
we
have
a
backup
that
can
run
in
the
interim
ice
in
factual
as
well
so
in
right
now,
Michael
to
sum
up
and
talk
about
how
datastax
or
cassandra
has
been
carefully
okay.
A
A
A
Security,
unimpeachable
availability
and
it
made
sense
if
there
had
been
more
of
a
focus
on
just
pure
document
database.
There
are
better
answers
out
there.
Perhaps
you
know
I
think
there
are,
but
what
Cassandra
came
through
for
these
guys
with
was
when
we
started
looking
at
kind
of
banking,
this
multinational
making
it
globally
available
and
having
to
span
multiple
cloud
providers
all
sudden
at
that,
you
know,
go
back
in
time.
Remember
this
is
23
years
ago
that
they
started
starting
builders.
There
was
no
such
thing
as
OpenStack.
A
There
was
no
such
thing,
as
you
know,
eucalyptus
there.
That
was
before
those
guys
are
fully
mature.
So
so
how
do
you
get
there?
The
answers
aren't
that
different
today
there
is
still
really
complicated
them.
Even
our
friends
at
Netflix
talk
about
being
eventually
portable.
That's
not
so
easy
what,
but
these
guys
did
that
two
three
years
ago
in
terms
of
our
fundamental
design,
and
I
think
that
the
when
you
look
at
those
business
requirements,
you
look
at
the
technology
requirements.
A
We
get
to
emit
an
interesting
point
where
we
said:
here's
the
right
news
case
for
this
technology,
a
distributed
database
that
can
span
clouds.
Okay,
that's
pretty
interesting
kind
of
you
know.
Cognitive
leap:
do
you
have
to
make
their?
I
think
that
you
know
when
you
start
looking
at
kind
of
the
consequences
of
systems
they're
going
to
be
looked
at
able
to
span
data
centers
to
be
able
to
span
clouds
the
answers
get
smaller
and
smaller
in
terms
of
what
the
viable
candidates
are
for
that
technology.
We.
A
Have
to
fix
counters,
we
have
to
do
a
lot
of
things
inside
of
the
Sandra
and
we
have
to
take
that
technology
and
moving
forward
with
the
data
section
and
price,
and
we
want
to
continue
to
engage
the
community
in
those
in
the
exploration
of
those
ongoing
solutions
so
that
we
can
actually
kind
of
say.
Ok
when
Jonathan
asks
you
guys
are
help
for
your
input.
We
need
your
input
because
we
can't
build
solutions
like
this
going
forward
without
your
help.
A
So
we
really
do
appreciate
the
contributions
of
community
in
many
different
ways
we
really
take
on.
We
relish
the
opportunity
take
on
new
business
challenges
and
new
opportunities
with
you
guys
together.
So
thank
you
very
much
for
your
contributions
and
thank
you
very
much
for
your
contributions.
We're
grateful
to
have
you
here
today.
We
look
forward
to
hearing
what
you
guys
come
back
with
when
all
is
said
and
done.
So.
Thank
you
very
much.
D
C
E
B
A
So
so
let
me
summarize
the
the
question
or
comment.
The
question
is
kind
of:
where
do
the
boundaries
or
responsibilities
lie
between
the
end
user
and
the
provider
of
the
system?
And
it's
a
complicated
question.
There's
no
good
answer.
It
means
you
know.
We
talk
about
medical
office
to
be
complicated.
Computer
ethics.
F
F
C
C
D
B
D
A
One
of
the
issues,
the
encounters
that
we
talked
about
before
was
you
know
the
the
programming
interfaces
were
not
there.
They
had
to
do
a
lot
of
work,
thrift
they
actually
had
their
own
RM
it
was.
It
was
illustrated
the
principle
that
you
know
we
talked
about
this
actually
a
life
in
touching
that
your
first
two
weeks
with
manga
or
your
tube.
This
week's
your
first
two
weeks
with
sander
are
your
tumor.
F
F
D
We
do
take
incremental
backup
and
that,
basically,
I
think
was
put
into
place
after
cassandra
side
supporting
incremental
a
backup.
Otherwise,
earlier
two
and
half
years
two
years
ago,
we
actually
had
to
take
the
entire
snapshot
and
then
do
it.
Of
course,
cassandra
has
been
evolving
to
provide
those
enterprise
level
support.
D
F
B
It's
kind
of
a
very
simple
answer
to
that.
Just
like
the
post
office
sender
pays
is
kind
of
waiting.
The
way
you
take
care
of
it,
so
the
people
that
are
paying
for
the
system
are
the
people
who
want
to
send
your
bills
and
they
want
to
send
them
cheaper.
So,
instead
of
paying
the
post
office,
they
pay
valley.