MagLev - From Download to Deploy
summary
MagLev runs Ruby on top of GemStone/S so code and live objects live in one image; the claim is native object persistence not just ORM mapping, and migrations change instance variables, method definitions and class hierarchies instead of SQL schemas. Demos show a job queue that stores and runs persisted blocks across machines, the stone attaching via a shared page cache to speed startup, and practical limits like non‑persistable IO handles.
AI-written summary · about
chapters (20)
- 0:00Intro
- 2:15History of Ruby
- 3:58byte magazine
- 5:59Smalltalk
- 8:24Backstory
- 11:10Why use Java
- 11:52Running on JRuby
- 12:42MagLev History
- 17:12Data Stores
- 18:34MagLev Overview
- 20:10Ruby Engine Overview
- 20:50Object Relational Impedance Mismatch
- 21:32Basic Examples
- 21:51Hat Trick
- 22:10Rails Demo
- 22:29abort
- 23:12persistent block
- 30:43geohash
- 32:20GitHub repo
- 32:41Outro
related talks
50mAllow me to reintroduce myself, my name is MagLev
33mData Migrations with MagLev
43mTANSTAAFL - Implementing Maglev Ruby on top of GemStone
53mRuby Persistence in MagLev
33mRuby Changed My Life
01h 03mStrengthening the Ruby Ecosystem Part II: Merb
01h 24mLightning Talks – Community Voices & Ruby Sparks
26mImmutable Ruby