4 ms·
I haven't maintained any sizable database system without any issues, least of all performance ones. I call BS.
by paulddraper 2y ago
I haven't maintained any sizable database system without any issues, least of all performance ones.
I call BS.
- tomnipotent 2y agoThis gave me a good chuckle, and has generally been my experience. Systems grow often in unpredictable or unintuitive ways. You can pay the cost for something upfront, and the cost of maintaining it, and in the long term paid too much for something you didn't actually need. Alternatively you can wait to pay it until you're certain you need it but the work involved has become much more significant, in which it can cost more than it would have to have built and maintained it from the beginning. Compounding the issue is the build-up-front scenario costs fade with time and you don't really think about them, but build-when-you-need-it always creates a stir even if the costs are less overall than build-up-front. Either way something will go wrong no matter how many times you predict where the cards will fall.
- netcraft 2y agolol, I of course don't mean that I have no issues, performance or otherwise. Only that I have never had an issue with UUIDs in postgres
- paulddraper 2y agoThe "issue" is that you're doubling the size of your identifiers, and increasing memory usage of indexes. And memory is the key factor of any sizable database.