But there's nothing in English like the words that were referenced in the German etymology. So the etymology can't be shared; the similarity of the expressions is just a coincidence.
FWIW, the OED (1973) says that the etymology of the English expression is from "wash" meaning "kitchen swill or brewery refuse as food for swine". It's just a variation of the reduplication of this term. So nothing like the German etymology.
@Gigili I always knew you're a likeable attacker :p
War einmal ein Bumerang; War ein Weniges zu lang. Bumerang flog ein Stück, Aber kam nicht mehr zurück. Publikum - noch stundenlang - Wartete auf Bumerang.
To me, it conjures up a happy little man skipping gaily across a hillside. Which it's meant to. But then, I know the music, so I'm singing it in my head.
If you try to have multiple shards, you end up adding a whole lot of logic to your application, to find which shard a particular item of data is going to be in. Then you get the practical issues of doing a join between two tables, where you want an item from one shard associated to an item from another shard. Most business models just don't divide up very easily that way.
Just don't ask me to express all of that in German! :-)
Good. By the way, I've been working with SQL databases since 1993; some sharded, some unsharded. I don't know too much about NoSQL though. Sharded databases create challenges that seem to pervade the entire application.
Like deadlocking issues, for example. It can be hard to restrict all these problems to just the data access layer of an application.
@hilbi I wouldn't know about NoSQL scaling without problems. It seems to me that it could be hype. They're not really mature technology; I'm sure there are problems, but nobody really understands them the way we understand the problems with SQL databases.
deutschsprachiger Raum
deutschsprachiger Raum