The tl dr is that developers tend to use UUIDs because: For more information about what a UUID is, please check out this article from Baeldung. Due to these complexities developers often use UUIDs (GUID for you C# developers). What should be an ID and what shouldn’t is a complicated subject, especially in a database where rigid rules are difficult to change after the fact, especially in modern development where both data and systems are distributed. Therefore, to nobody’s surprise, I care a lot about:īoth of which. I care about the long term sustainability of what we’re making. If I had to choose which aspect of software development I am most passionate about it would probably be how we make our products, which includes things like what kind of standards we follow when writing code, which tools we use, how we get our final code into production in a safe manner. toUUID() to toUUID).įor the latest information, take a look at the toUUID Github repository.įor a better writeup on the pros and cons of toUUID, with more examples, check out the why toUUID? file on Github. While most of the points made in this remain relevant, there are some syntactical changes, and other minor updates (also a re-branding from. Since toUUID was released it has gone through some changes which is not reflected in this post.
0 kommentar(er)
