Unboxing Ruby Box

Introduction of Ruby Box and its use-case at Ruby Release 30th Anniversary Party #rubyrelease30th

Transcript

1. Ruby Release 30th Anniversary Party Unboxing Ruby Box 2025-12-20, Satoshi Tagomori (@tagomoris)
2. ా᝷ ૱ (Satoshi Tagomori) @tagomoris ͘͞ΒΠϯλʔωοτ (2024.08ʙ) Ϋϥ΢υࣄۀຊ෦ ϓϩμΫτϚωʔδϟ Maintainer/Founder: OSS: Ruby, Fluentd, MessagePack, 
 Norikra, Woothee, …
 Event: ISUCON Service: Pathtraq
3. https://www. fl ickr.com/photos/takkanm/3978417669 Asakusa.rb
4. Product Manager, SAKURA Cloud (2024-08-01 ~)
5. めりー 2025-12-20
8. Unboxing Ruby Box Introduce the use cases of Ruby Box • What ’ s “Ruby Box”? • Naming • Feature • Testing in boxes • Running boxes • Playing with boxes
9. What ’ s “Ruby Box”? Naming Feature
10. What ’ s “Ruby Box”? An experimental feature introduced in Ruby 4.0!
11. Naming What ’ s “Ruby Box”? • Ruby Box • Renamed from “Namespace” after RubyKaigi 2025 • Accessed as “Ruby::Box”
12. Naming What ’ s “Ruby Box”? • Ruby Box • Renamed from “Namespace” after RubyKaigi 2025 • Accessed as “Ruby::Box” • NO MORE “Namespace”!
13. Feature What ’ s “Ruby Box”? • Separating apps/libs into isolated spaces • Load apps/libs in a space • Hide changes from apps/libs in the space to others • Run methods de fi ned in the space with the de fi nition
14. Before Ruby Box: Global Only All classes/modules are shared in the entire Ruby process Ruby Process Application Code App::Func User Library Code DB::Client (v2) Library Code ActiveSupport (v7)
15. Before Ruby Box: Global Only Monkey patches overwrite things globally Ruby Process Application Code App::Func User Library Code DB::Client (v2) Library Code ActiveSupport (v7) class String def +(other) = “self:#{other}” User Library Code
16. Before Ruby Box: Global Only Monkey patches overwrite things globally Ruby Process Application Code App::Func User Library Code DB::Client (v2) Library Code ActiveSupport (v7) class String def +(other) = “self:#{other}” 😵 😵 😵 User Library Code
17. Ruby Process Ruby Box Using Ruby Box Ruby Box provides separation for funky monkey patches! Application Code App::Func User Library Code DB::Client (v2) Library Code ActiveSupport (v7) class String def +(other) = “self:#{other}” User Library Code 😀 😀 😀
18. Ruby Process Ruby Box Using Ruby Box Ruby Box can load different sets of applications&libraries! Application Code App::Func User Library Code DB::Client (v2) Library Code ActiveSupport (v7) Ruby Box Application Code App::Func User Library Code DB::Client (v3) Library Code ActiveSupport (v8) "QQ
    XJUI
    0MEFS
    MJC
    WFSTJPOT "QQ
    XJUI
    /FXFS
    MJC
    WFSTJPOT
19. Use Cases?
20. Testing in boxes
21. Ruby Process Testing in boxes Don ’ t you need a funky monkey patches in tests? • Applications tests sometimes need monkey patches • to mock library behaviors, IO objects, … • Most of tests can run without box. Just some of them can ’ t. • How about running tests in boxes? • Running all tests in boxes is too expensive • Run just some of them in boxes! Ruby Box Application Code Test Case Monkey Patches Test Case Test Case Test Case Test Runner
22. Let ’ s Try!
23. Did it work well?
24. More Use Cases?
25. Running boxes
26. Ruby Process Server Ruby Process Server Running Boxes (1) Library/middleware updates • You ’ re trying to update library versions of your app • Blue-green deployment using cloud services • Long-term parallel testing • Hard things • Building and keeping those infra components • Verifying responses (only with status, without Ruby code) "QQMJCT
    WFS
     "QQMJCT
    WFS
     Load Balancer 4FOE
    SFRVFTUT
    7FSJGZ
    SFTQPOTFTʜ
27. Server Ruby Process Ruby Box Ruby Box Running Boxes (2) Library/middleware updates • Running 2 sets of apps/libraries in 2 boxes • You can run 2 sets in a Ruby process • You can use Ruby code to check diffs! "QQMJCT
    WFS
     "QQMJCT
    WFS
     Application Server 3PVUF
    SFRVFTUT
    BT
    VTVBM
    7FSJGZ
    SFTQPOTFT
    VTJOH
    3VCZ
    DPEF
28. Let ’ s Try!
29. Sorry, It ’ s still experimental…
30. Playing with boxes
31. Play, and Fix Ruby Box Way to exit EXPERIMENTAL • Fix bugs • It still crashes (as you see) • Design new ways to • Provide hook points (box hides methods) • Stop using global variables (box hides global variable changes) • Work together with RubyGems • RubyGems has internal states (calling RubyGems from boxes doesn ’ t work)
32. Play, and Fix Ruby Box WE NEED YOU! • There should be corner cases! • I need reports from various environments • You can fi nd new bugs of Ruby Box • You can fi x something for Ruby Box! • Libraries, middleware, …
33. Enjoy Ruby 4.0! with Ruby Box! And, teach me your interesting/funky use cases of boxes!