partitioned

It means you're not running a partitioned and distributed system, but a regular non-partitioned system.

No, that means specific problem domains that are not easily partitioned, and where latency or affinity are the primary performance constraints.

In other words you would have a single topic partitioned by user id, not a topic per user.

The county decided to split the property, partitioned his home and sold half of it to someone else.

Matrix IDs themselves are completely decentralised, just like Jabber IDs, and are indeed fully partitioned by domain.

One thing to realize is that a partitioned log is a generalization of an unpartitioned log (i.e.

Assuming you have a huge log table, partitioned by week, would this be a better fit?

Perhaps Tarsnap makes sense if you're Stripe, with lots of sensitive data to store, easily partitioned from your other data.

What you usually have is (at best) a per partition ordering, which maps well to a partitioned log as well.

Next, you don't have to over-provision unpartitioned space AND preserve 20% of partitioned free space.

There are dual-use systems which run classified and non-classified codes (they can be partitioned..

They're there, just the subsystems partitioned into multiple namespaces under a single host.

Even more interesting, could dark matter be partitioned into various categories based on the "boson" they interact with?

I brought this up on Twitter, but I think the term "shard" referring to a partitioned database originated from Ultima Online.

The one thing I'm always somewhat confused by though is how a "totally ordered log" intersects with the reality of a partitioned log.

It is based on the idea of having a unified approach for shared memory and distributed system and accomplishes that by assuming that objects can be partitioned into disjoint ("separate") data spaces, access to which is regulated to ensure mutual exclusion; this is why it translates nicely to a model involving thread-local heaps.