Would you like to forget about the database?

on YouTube ↗30m

" summary

Argues that Maglev on the Gemstone S VM gives transparent object persistence: Ruby objects live in a shared image, persisted via a persistent-root hash and ACID transactions (abort/commit) instead of SQL or JSON. Demonstrates a working Sinatra blog and a background-job queue implemented in ~34 lines, shows arrays vs Gemstone’s reduced-conflict Q for concurrency, and explains persistence by reachability where related objects auto-persist. Claims compatibility with many gems and roughly matches Ruby 1.8.7/1.9.3 performance.

AI-written summary · about

" chapters (8)

1. 0:00The object database problem
2. 1:39Impedance mismatch explained
3. 4:46Introducing Gemstone S
4. 7:07Transparent persistence
5. 10:12MagLev architecture
6. 14:02Building with MagLev
7. 17:48Background jobs and queues
8. 22:57Future and Q&A

" related talks

• 50mAllow me to reintroduce myself, my name is MagLevJeese Cooke · RubyConf 2012
• 35mPersisting Relations Across Time and SpacePiotr Szotkowski · RubyConf 2011
• 53mRuby Persistence in MagLevBob Walker, Allan Ottis · RubyConf 2008
• 40mPutting off PersistenceLauren Voswinkel · GoRuCo 2013
• 32mRuby PreservesCraig Buchek · RubyConf 2015
• 36m"Persistence pays off: a new look at rom-rb"Piotr Solnica · RubyC 2017
• 01h 12mHidden pearls for high-performance-persistence in JavaSven Ruppert · Joker 2020
• 26mRuby APIs for NoSQLSarah Mei · GoGaRuCo 2010