loiselleatwork

It sounds like you underestimate the enthusiasm for miniatures in general. There is a lot of demand for finely printed models––look at Tribes on MyMiniFactory, or the success of primarily 3D printed games like Trench Crusade.

On the other side of this _is_ the affordability of 3D printed miniatures. The linked-to article is salient/cogent/great, but the secondary topic at hand––lowering the price of entry for miniatures-based table top gaming––is still salient. 3D printing won't necessarily upend GW's business model, but it does provide an entry point that is more affordable by some calculus.

CockroachDB, but it was conceived of in Go

Author of post here and CRL employee: just for some additional detail, we reached out to Kelsey about the problems he's seen running databases in Kubernetes.

https://twitter.com/kelseyhightower/status/96347131657256140...

He said "You still need to worry about database backups and restores. You need to consider downtime during cluster upgrades."

These things are totally true. K8s doesn't automate backups (edit: by default; though, it can) and if you need to take K8s down for upgrades, then everything is down. For its part, though, CockroachDB supports rolling upgrades with no downtime on Kubernetes.

As for routing, that is tough problem if you want to run K8s across multiple regions, though we have some folks who've done it.

And if one finds setting up StatefulSets challenging, we have a tutorial on how to do it written by a former Kubernetes engineer: https://www.cockroachlabs.com/docs/stable/orchestrate-cockro...

We call it CRDB internally

This is super interesting; thanks for the pointer.