Data Migrations with MagLev
summary
MagLev runs on GemStone/S and claims to persist plain Ruby objects including procs and lambdas via a shared page cache that attaches VMs on login. The runtime uses a commit abort transactional model for fresh object views and raises commit-failed exceptions for conflicts. Live demos show persisting strings and procs, a migration that adds a date field to old blog posts, and using object become to swap class identities. Limits include 2 gig shared page cache and a 10,000 session cap while Ruby compatibility sits near 1.9.3 and production use is planned at CreditTera.
AI-written summary · about
chapters (9)
- 0:00Start
- 0:49Outline
- 1:06What is MagLev?
- 1:18What is GemStone/S?
- 2:24Why MagLev
- 3:23Typical Rails Stack
- 5:11Transactional Memory
- 6:19Let's persist some stuff
- 24:47Project Status / FAQs
