3 ms·
He's not saying clients can create their own ids. The applications can. The concepts he's talking about are required for cqrs. Which is a popular concept appli
by NicoJuicy 5y ago
He's not saying clients can create their own ids. The applications can.
The concepts he's talking about are required for cqrs. Which is a popular concept applied with mostly DDD or microservices.
- inopinatus 5y agoI getcha, but these days the ambit reach of "application" extends to Javascript executing client-side in an environment that's basically overrun with lions/tigers/bears, and I'll suggest that's particularly a consideration when the front-end is a SPA participating in a CQRS/event-sourced overall application architecture.
- tomnipotent 5y agoFor perspective, the npm uuid package is now being downloaded ~50M/week. It's usage is ubiquitous at this point, on any platform JS is running. https://www.npmjs.com/browse/depended/uuid https://www.npmjs.com/browse/depended/uuid
- NicoJuicy 5y agoLittle bit later to reply. Unfortunately that doesn't mean much. Since nodejs is a server side language and can handle that package too. And it's not "solely" for js/spa's.
- lazide 5y agoThere definitely are people out there in this thread proposing clients be able provide UUIDs. I’ve seen it elsewhere too. I’ve also personally experienced UUID collisions due to badly set up VM environments under Windows. It isn’t a good idea to blindly trust any value - and that includes supposedly ‘never collide’ id’s like UUID. For what it’s worth, I also had the joy of debugging someone’s distributed hash table that was using md5 as the hash bucket key (this was... 2 decades ago?) and had no way to handle collisions because obviously that is impossible.
- NicoJuicy 5y agoThis seems more an issue of the libraries random generator to form uuids. Eg. I use guids ( .net) and i have never seen an issue.