I've recently stumbled on a Marco Pivetta's PHP Conf speech about Doctrine Best Practices and Tricks, and i really like solutions and the whole idea of immutability.
Even tho, if one wants to achieve Immutability, he cant use auto-incremented integer strategy anymore, because it would break the immutability concept, and Uuid's come in handy here i understand it, but my concern is how it will affect my database performance, *and at the end of the day, would it be worth of implementing Uuid's just for the sake of immutability.* I don't have much experience in Uuid's but recently i've been researching this topic, and im aware that Sequenced Uuids exist, and they are much easier to index than totally random ones, but its still unclear to me, should i take this as solution to my business logic or not, because there are a lot of debate's on this topic on forums going back and forth, too many opinions and im unable to make decision. *Anyway, question is, is there big performance issues when it comes to reading and inserting data, also when working with joins and relationships,if i use Uuids, and also, what would be ideal implementation of them for sake of better performance ?* Btw im working in MySql, if that helps. Even tho i would really like to see Pivetta's answer, any help or answer would be highly appreciated. -- You received this message because you are subscribed to the Google Groups "doctrine-user" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/doctrine-user. For more options, visit https://groups.google.com/d/optout.
