> When speed matters, you have to get the compute and the data as close as possible.
And when scaling matters, you often need to do the opposite. And scaling is often more important than speed.
And when scaling matters, you often need to do the opposite. And scaling is often more important than speed.
Yes, often doesn't scale because the database is an extremely limited resource that generally doesn't scale horizontally.
> or you can move the data to the compute
Which is what I said, which allows you to scale computation horizontally.
> There is no situation ever
You just named one, however I see where you're misinterpreting me or I you; when I said do the opposite, I meant move the computing away from the database.
But anyway, that's what indexes are for in RDBMS, so you still have a point, even figuratively :)