Fluence Labs / Aquamarine

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

Speaker: Bernhard Borges, Fluence Labs

Timecodes:
00:00 Intro
00:14 Fluence Labs. Peer-to-peer infrastructure.
02:21 The need for distributed programming tools. How the Request-Response differs from client-server and peer-to-peer application
04:29 Aquamarine programming language
06:48 Aquamarine foundations: inspired by π-calculus
07:56 Aquamarine foundations: particle — data structures combining data, execution, sequence, and metadata
08:12 Aquamarine Instructions, Aquamarine Intermediary Representation, low-level Aquamarine language
10:07 Particle — data structure combining data, execution, sequence, and metadata
11:21 Aquamarine VM + Aquamarine Languages
14:23 Building with Aquamarine
16:00 Aquamarine in Action: Basic SEQ (iterate over results "manually")
18:17 Fold SEQ (iterate programmatically)
21:59 Security
24:37 Greeting app example
26:35 "fldist" Aquamarine tool
33:09 Recap
34:59 Q&A: Is there a way to trace the routing path which a particle took? How do we debug what went wrong?
38:56 Q&A: Could you elaborate on fault tolerance and error handling within scripts with XOR operation and %last_error%?
42:03 Aquamarine from the problem-solving perspective
50:40 Q&A: How do we maintain latency SLA’s? can we have strict performance characteristics for each peer in the network?


Greeting app:
https://github.com/fluencelabs/examples/tree/main/par-greeter
Get started with Fluence https://fluence.gitbook.io/docs/
Protocol Paper https://github.com/fluencelabs/rfcs/blob/main/0-overview.md
Dashboard https://dash.fluence.dev/​
Github https://github.com/fluencelabs​
Fluence Home https://fluence.network/