(...) Phoenix on Riak_Core

on YouTube ↗38m

" summary

Claim: co-locate app servers and the DB by running Phoenix on top of riak_core to get in-memory, shardable state with replication. Tools actually used: Erlang VM, ETS for per-vnode storage, consistent-hash ring, vnode write coordinator with N and W (demo uses N=3 W=2), handoff for rebalancing, and a pubsub adapter that shards topics so Phoenix channels sharded by topic handle subscriptions on specific vnodes. Demo across multiple VMs stores, fetches and replicates data successfully but remains experimental.

AI-written summary · about

" chapters (15)

1. 0:00Intro
2. 0:43Stateful Architecture
3. 4:13Stateless Architecture
4. 6:10Stateful Web Application
5. 7:13Distributed Systems
6. 9:04CAP
7. 10:56RiakCore
8. 11:24How it works
9. 18:24Store Fetch
10. 20:57Fault Tolerance
11. 21:26Write Coordinator
12. 24:50Handoff
13. 25:41Phoenix in RiakCore
14. 28:56Phoenix in RealTime
15. 30:35PubRing

" related talks

• 01h 00mPhoenix a Web Framework for the New WebJosé Valim · GOTO Copenhagen 2016
• 45mPhoenix a web framework for the new webJosé Valim · Lambda Days 2016
• 32mWhy I choose PhoenixAaron Cruz · RubyConf TH 2022
• 29mRails to PhoenixBrian Cardarella · RailsConf 2016
• 41mElixir & Phoenix – fast, concurrent and explicitTobias Pfeiffer · RubyConf Portugal 2016
• 01h 00mPhoenix: an Intro to Elixir's Web FrameworkSonny Scroggin · NDC London 2017
• 50mPhoenix Framework: a (Truly) Fullstack Stack for Building Real-Time WebMaxime JANVIER · Sunny Tech 2024
• 44mElixir & Phoenix - Fast, Concurrent and ExplicitTobias Pfeiffer · Øredev 2019