[tyre]

Multi-database support is not "basic". At what point do you need that? What percentage of users do?

Regardless, it was fully supported in gems for years before it went into Rails. It's nice to have it in core. But to say that Rails doesn't feel mature without it?

Come on.

[yxhuvud]

Of six rails shops I've worked on, half used connection to a secondary sql database in one way or another. Exact use cases has differed but I wouldn't be surprised if it is actually a rather high percentage of medium sized to big apps that use multiples.

[zbentley]

> At what point do you need that? What percentage of users do?

In my experience, rather a lot.

[obiefernandez]

If you need to connect to multiple databases at a time for your business logic then you're doing it wrong.

[zbentley]

...are you serious?

Virtually every software shop I've worked at has had most backend code communicating with multiple databases to get the job done. Sometimes those databases were behind [micro]service abstractions and the communication was indirected by RPC/one-way async dispatch. Sometimes it wasn't. But multiple backend datastores' contents were required for most business operations. The only places I've worked with that didn't need that were very, very small (single digits of thousands or fewer users).