►
From YouTube: Approaching Web3 With Aqua Language
Description
How Aqua language and Fluence network enables the transition from web2 to web3 paradigm and why it matters
0:00 Intro. Approaching Web3 With Aqua Language
0:22 Transition from Web2 to Web 3 Peer-to Peer.
1:36 Web 2 distributed approach
4:09 What is peer-to-peer. Why to choose p2p. Motivation for Web 3
7:33 Distributed:Why? Mindset of Web 2
10:50 Peer-to-peer : how? Mindblow of Web3. Part 1 "Security"
13:23 Peer-to-peer : how? Mindblow of Web3.
Part 2 "Lot's of questions"
15:36 Peer-to-peer : how? Mindblow of Web3.
Part 3 "Tool set"
18:22 When you meet the WHY...
21:25 When you don't meet the WHY...
23:47 Bridge the worlds. Distributed and peer-to-peer
AQUA
26:02 Aqua fills gap between Web2 and Web 3
27:27 How can we approach problems with aqua
28:56 Discovery primitives
32:57 State sync primitives
35:27 APIs and logic
38:15 Operations
39:34 Developer experience
42:55 Maintenance and creativity
44:04 Mailbox
45:15 Scheduler
46:03 Economy
47:06 What aqua looks like
Website: fluence.network
Discord support https://fluence.chat/
Telegram : t.me/fluence_project
Twitter: @fluence_project
Careers: fluence.one/join.html
Speaker: Dmitry Kurinskiy, Fluence Labs CTO
Resources
https://fluence.network/
https://twitter.com/fluence_project
https://github.com/fluencelabs/aqua
https://github.com/fluencelabs/aquavm
https://github.com/fluencelabs/marine/tree/master/examples/greeting
https://fluencenetwork.notion.site/fluencenetwork/Fluence-Developer-Community-Calls-2733beddb3ff4e4986c4fcc830fc796d
https://github.com/fluencelabs/marine-rs-sdk
https://t.me/fluencedev
https://discord.com/invite/5qSnPZKh7u
A
A
To
use
it
efficiently
and
we
have
a
lot
of
products
like
the
one
that
we
are
using
right
now,
which
merges
from
this
setup
and
now
probably
we
we're
switching
to
web
three,
but
let's
discuss
why
we're
doing
it,
and
what
does
this
mean
and
let's
discuss
it
in
comparison,
web
2
and
web
3?
What
we
had
what
we
have
and-
and
why
so,
first
of
all,
let's
speak
about
the
common
web
to
distributed
approach.
A
A
A
A
A
A
So
that's
why
I
want
to
be
distributed
cool
and
why
won't
would
I
want
to
have
something
in
web
3,
so
web
3?
First
of
all,
what
is
it
it's
about
being
peer-to-peer?
Not
just
distributed
but
more
decentralized,
more
peer-to-peer,
more
permissionless,
so
the
motivation
for
web
3
first
of
all
is
economy
and
governance.
A
It
doesn't
always
mean
to
make
money,
but
it
means
that
you
have
the
new
ways
to
create
something
and
to
scale
something
and
that's
that's
important,
and
then,
after
the
economy,
there
are
different
properties
that
are
also
nice
to
have
and
which
actually
make
the
web.
Three
were
three
like
no
single
point
of
failure.
No
vendor
lock-in,
that's
nice
and
that's
a
property
of
a
peer-to-peer
web
3
permissionless.
A
If
you
build
a
peer-to-peer
network,
if
you
make
it
accessible
to
everyone,
if
you
make
it
open
source,
then
it
means
that
you
open
the
doors
for
creativity
and
the
community
can
be
involved
if
you
build
another
cloud
or
another
api
and
so
on.
There
is
no
incentive
to
be
involved,
because
we
have
so
many
cases
when
enterprises
uses
the
community
creativeness
and
then
just
closes
the
door.
A
A
A
A
A
Usually
you
have
some
kind
of
mailboxes
and
for
mailboxes
you
have
managed
queues,
kafka
and
so
on
to
connect
different
parts
of
the
application.
You
have
persistence
and
for
persistence.
You
have
many
choices
like
key
k,
value
stores,
journals,
write,
catalogs,
different
databases
for
any
shape
of
data,
and
so
on
then,
for
scaling
and
operations.
You
have
kubernetes
for
service
discovery,
you
have
console
and
generally
speaking,
you
have
dns
and
so
on,
and
you
have
data
centers
virtual
networks
for
connectivity
between
them,
some
side,
cars
for
connectivity
like
easter
and
and
so
on.
A
So
basically,
I
can
decompose
the
problem
of
a
distributed
web
2
back
end,
and
I
know
how
to
start-
and
I
know
why
why
everything
will
be
okay
and
I
don't
need
always
to
get
everything.
But
if
I,
if
I
take
almost
any
approach,
probably
it
will
have
some
solutions
for
every
part
of
that,
for
example,
if
you
take
actor
system,
then
it
has
its
own
mailbox
for
every
actor.
You
have
mailbox,
you
can
switch
on
persistence
and
have
write
head
log,
you
can
scale
and
it
has
some
primitive
automatic
scaling
with
akka.
A
A
A
A
If
I
don't
want
to
be
deterministic,
then
the
question
is
how
to
synchronize
my
peers.
Do
I
want
to
have
eventual
consistency
or
no
consistency
or
how
to
approach
it
and
what's
the
right
algorithm
at
this
point,
I
can
think
about
the
network
algorithm
and
then
the
question
is
okay.
I
have
these
nodes,
but
what
is
the
business
model?
How
can
I
make
the
development
self
sustainable
and
how
can
I
incentivize
the
community
to
like
to
to
provide
creativity
to
commit,
inter
into
this
web
three
projects?
A
How
to
distribute
the
tasks
and
like
that's
another
question,
and
we
have
some
solutions.
For
example,
you
can
have
inflation
or
you
can
have
a
mining
reward
or
you
can
have
something
that
like
that.
But
for
every
solution
you
have
constraints
and
there
are
not
so
many
choices
here.
Actually
and
finally,
after
I
consider
security
and
I
keep
it
in
mind
and
then
I
made
a
lot
of
decisions
on
the
domain
of
my
web3
application.
A
A
But
then
I
can
make
a
smart
contract
on
a
blockchain,
for
example,
and
that's
one
way:
that's
open,
you
can
do
it
and
we
have
a
lot
of
different
businesses
around
some
smart
contracts
or
you
can
move
to
layer
two.
If
a
big
block
chain
like
ethereum
is
not
overkill
and
we
have
some
layer,
two
solutions
like
substrate,
but
then
we
still
have
some
questions
and
it's
it's
hard
to
answer
them
in
the
in
the
current
landscape
of
web
three
toolsets
like
scalability,
okay.
A
A
A
A
Am
I
able
to
to
meet
the
motivation
of
doing
web
3
or
I
have
to
compromise
and
what
the
compromise
looks
like
so
often
when
the
tool
set
cannot
be
in
part
with
a
web
2
distributed
tool
set
or
a
mindset
for
a
particular
use
case,
then
the
wires
can't
be
met,
the
wise
of
web3
and
the
choice
is
actually
web
2.
and
why?
Why
is
it
bad?
Is
it
bad
at
all?
Is
it
good
or
bad?
A
A
A
The
the
easiest
way
is
to
not
be
able
to
solve
how
and
if
you
don't
solve
the
how
of
web
three,
how
exactly
to
build
your
system?
How
exactly
to
approach
your
business
opportunity,
then
there
could
still
be
an
opportunity
to
create
a
web
to
business
like
sas,
and
we
have
some
cases
when
we
see
that
web
three
specific
problems
are
fixed
by
centralized
web
to
driven
businesses.
A
A
You
and
europe
also
develop
and
you're,
locking
in
and
so
on.
Is
it
good
or
bad?
I
think
neither,
but
I
believe
that
in
in
the
in
the
better
world
the
for
every
important
problem
in
the
emerging
web
3
ecosystem,
there
should
be
a
couple
of
web
2
solutions
to
have
three
specific
problems
and
a
couple
of
web
three
solutions.
A
And
often
we
see
that,
for
example,
for
infuria,
we
have
alchemy
right
and
we
have
something
like
oct
network,
and
I
know
about
a
lot
of
different
approaches
to
decentralize
this
ethereum
access,
but
with
the
with
no
luck.
No
luck
compared
to
you
run
because
it's
very
hard
to
to
build
to
maintain
to
evolve,
because
there
are
many
questions
how
to
do
it
so
would
be
nice.
It
would
be
nice
to
bridge
the
worlds
and
what
does
that
mean?
A
A
A
A
Let's
take
a
look
on
them
again
in
like
no
weather,
login,
option,
source
censorship,
resistance
data
ownership,
deep
platforming
protection
and
so
on
and
the
connection
to
the
new
economy
as
well.
That's
that's
important,
and
to
do
so,
it
would
be
nice
to
solve
the
house
of
web
3
in
par
with
web
2
and
the
problem
of
building
a
web
2
back
end
a
web
2
application
a
distributed
web
application
is
very,
very
well
thought.
A
So,
for
example,
with
aqua
you
can,
you
can
have
discovery
primitives
like
in
web
2.
We
have
many
developed
projects
which
evolved
over
decays
or
at
least
years
like
console,
zookeeper
or
dns,
and
the
console
means
that
you
have
a
consensus
based
on
raft
consoles
is
essentially
a
raft
algorithm
and
nothing
more
and
zookeeper
is
the
is
what.
A
Foxus
right,
it's
also
the
algorithm
and
both
algorithms
can
be
implemented
in
aqua
for
non-global
discovery
for
application,
specific
discovery,
but
generally
aqua
and
flints
provides
for
web3.
First
of
all
academia,
and
currently
we
are
using
the
lip
b2p
implementation
of
cadanglia,
but
we
are
going
to
switch.
A
A
So
it
lowers
the
barrier
dramatically
because
you
don't
need
to
run
your
own
network
to
have
your
own
network.
You
can
deploy
a
sub
network
on
existing
nodes
and
you
can
prioritize
the
discovered
the
connections
between
these
nodes
over
the
general
usage
we
have
registry.
It's
previously
was
known
as
aqua.ht.
A
Now
we're
going
to
switch
to
the
registry
name,
it's
like
ipns,
but
not
exactly
ipns.
So
it's
work
in
progress,
sub
networks,
his
work
in
progress
protocols,
his
work
in
progress,
and
what
does
mean
that
it's
a
work
in
progress?
It
means
that
we
identify
these
problems
and
we
understand
that
to
get
in
part
with
a
web
tool
and
to
provide
the
best
experience
for
developers.
A
A
A
Next
about
the
stage
synchronization
in
web
2.
We
have
a
databases
of
any
scale
for
any
data
shape
like
we
have
anything
for
web
3
is
much
harder,
but
we
have
blockchains
big
and
small
of
various
shapes
and
different
algorithms
and
with
aqua
influence
you
can
proxy
requests
to
to
blockchains.
You
can
delegate
state
synchronization
to
blockchain.
If
you
want
to
and
it
could
be
ethereum
you
can
read
from
ethereum,
you
can.
A
A
A
Everything
is
is
a
bit
harder
because
you
know
about
the
problem
of
a
blockchain
bridges.
For
example,
it's
not
not
trivial
to
get
data
from
one
storage
to
another
storage.
If
you
consider
a
blockchain
as
a
storage,
for
example,
but
with
aqua
and
marine,
you
can
access
apis
and
services
from
from
aqua
and
you
can
bring
services
or
you
can
bring
existence
existing
code
basis
to
this
web
3
setup,
which
sometimes
very
efficient
and
like
good,
that's
what
we
did
with
the
ipfs.
A
A
The
next
problem
is
operations,
hence
capability
in
web
2.
We
have
a
lot
of
tools
like
terraform,
kubernetes,
docker
and
so
on
for
web
3.
It's
time
to
replace
docker
with
web
assembly
and
with
marine.
We
have
effects
access
with
the
help
of
webassembly
because
it's
sandboxed
it's
secured
and
it's
safe
to
expose
the
capabilities
of
the
node
to
the
outer
world
with
the
with
web
assembly.
It's
much
much
more
secure
than
doing
doing
so
with
docker.
A
Then
a
couple
of
words
about
developer
experience
in
web
2.
We
have
a
lot
of
tooling
to
to
protect
from
from
common
bugs
and
problems,
and
usually
this
is
a
this
critical
just
super
critical
to
have,
for
example,
akka
started
untyped,
but
its
development
with
a
untyped
akka
is
barely
doable.
It's
super
hard,
it's
extremely
hard
and
not
a
lot
of
people
can
can
do
it
without
the
proper
typing
and
the
proper
patterns.
A
So
I
believe
that
if
we
want
to
commoditize
web3
development
and
if
you
want
to
make
it
accessible
to
people
and
to
unlock
the
possibilities
of
these
different
businesses
with
the
web
3
values,
we
need
to
to
provide
the
developer
experience.
That
is
close
to
the
solutions
to
the
web
to
solutions
that
aims
on
the
same
problem.
A
A
A
You
can
do
you,
you
have
this
simple
mailbox
for
every
service
on
every
period,
but
it's
kind
of
limited,
just
like
in
inaka.
The
built-in
mailboxes
are
very
simple,
but
with
aqua
you
can
do
the
more
complex
patterns
like
back
pressure,
pulling
persistence
and
so
on,
and
probably
the
generic
solution
for
this
problem
of
mailboxes.
A
But
the
simple
solution
is
already
here
with
the
service
mail
boxes,
then
there
is
a
problem
of
shadower
when
you
need
to
shuttle
the
tops
and
to
distribute
to
the
workload
among
the
peers
in
web
2.
We
have
a
lot
of
solutions
in
web.
3
affluence
provides
scheduler
for
aquascripts,
it's
very
simple:
it
just
runs
some
script
currently
and
it's
probably
the
the
most
primitive
shadowers
of
web
2
like
the
built-in
cat
scheduler,
for
example,
more
complex
things
to
be
invented.
So
it's
already
here
as
a
fundamental
solution.
A
It
needs
to
be
improved
at
least
and
for
economy
for
the
connection
with
all
the
all
the
new
economy,
it's
more
about
fluency
than
about
aqua,
but
in
web
2.
When
you
begin
the
new
project,
you
have
a
lot
of
options
like
subscriptions
application
marketplaces
and
for
web
3.
You
also
have
some
options
like
crypto
dolls,
or
something
like
that.
A
We
want
to
implement
some
sound
mechanics
later
as
a
part
of
the
fluency
stack,
but
dolls.
If
you
have
a
dial
on
on
some
blockchain
with
a
a
limited
effort,
you
can
connect
this
down
to
fluent
speakers
with
a
like
managed
whitelist,
for
example,
and
that's
planet.
That's
not
not
work
in
progress,
but
will
be
soon
and
that's
also
important.
A
A
A
That's
a
tiny
snippet
of
a
hello
world
made
trivial
finally
and
trying
in
a
web
3d
peer-to-peer
fashion
in
four
lines
of
code,
so
it
seems
very
simple.
You
say
that
you
want
to
call
some
function
somewhere
and
you
want
to
get
to
this
place
through
some
relay,
but
actually
it
involves
all
these
signatures,
different
attacks,
protection
and
and
all
the
stuff
to
make
it
trivial
like
it,
has
a
lot
of
complexity.