Skip to main content

RubyConf Thailand 2026 - Cell-Based Architecture

·146 words·1 min
Kostiantyn Lysenko
Author
Kostiantyn Lysenko

Last weekend at RubyConf Thailand 2026, note 2:

Watched a talk on cell-based architecture in Rails by Roonglit Chareonsupkul.

And I really like the idea of limiting blast radius. Not only for Rails, for any kind of stack.

A cell is a self-contained slice of your system - its own app instances, database, cache, queues. You replicate cells and route users/tenants to specific cells.

Also cells play well with canary deployments. Deploy new version to one cell first, verify, then roll out to others. If something breaks - bad code, bad migration, resource leak - only that cell’s users are affected. Others keep running on their own isolated stack.

Without cells, canary helps with gradual rollout, but all users still share the same DB and infra. With cells, you get canary + hard isolation.

The bulkhead pattern from ships: one compartment floods, the rest stay dry.

Bulkhead pattern - cell-based architecture

comments powered by Disqus