Kerrick Long (code)<p>I've seen a lot of content about using <a href="https://ruby.social/tags/DDD" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>DDD</span></a> (Domain-Driven Design) with <a href="https://ruby.social/tags/Ruby" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Ruby</span></a> on <a href="https://ruby.social/tags/Rails" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Rails</span></a>, but none of it has addressed how to do the "one database per bounded context" pattern--especially in the world of Solid* and SQLite by default.</p><p>Does anybody have any strategies for this?</p><p><a href="https://ruby.social/tags/Programming" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Programming</span></a> <a href="https://ruby.social/tags/RubyOnRails" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>RubyOnRails</span></a> <a href="https://ruby.social/tags/DomainDrivenDesign" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>DomainDrivenDesign</span></a> <a href="https://ruby.social/tags/RailsConf" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>RailsConf</span></a> <a href="https://ruby.social/tags/RailsConf2025" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>RailsConf2025</span></a> <a href="https://ruby.social/tags/Architecture" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Architecture</span></a> <a href="https://ruby.social/tags/SoftwareEngineering" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>SoftwareEngineering</span></a></p>