Thanks for pointing that out. Reading this, you may run into issues whenever you have incrementing values in a document - which imho is hard to impossible to avoid if you want a sensible document logic, e.g., it is important to have certain timestamp-based properties in a document. Using a timestamp-derived (decreasing in my case, not increasing) prefix is also not the full ID, there is still plenty of other stuff you can add after that, e.g. in my example, it is "{{timestamp-derived-prefix}}_{{actualID}}".

That being said, the issues with hotspots seem to potentially arise only in very high-volume conditions (e.g. >500 document creations per second), my stuff never even comes close to such intensities, and as Google points out, in such cases, best practice would be to then start slow and then increase the volumne (500/5/5 rule).

I will add it as a note to the article though for those working in very high-volume environments.

Again, thanks for showing me this!