Hi Christian, guids is the most accepted datatype because of the easy to use and knowledge, but some huge databases note that this cause fragmentation, more storage and will generate memory pressures. For a normal application the guids is the best option. I don't have experience implementing different cases but Take a look into this article of someone that needed to change the guids for a new option:
https://www.sqlservercentral.com/articles/an-alternative-to-guids

>Hi, I am wondering if there is a very good reason to use guid data type over nvarchar(36)? Usually I am trying to avoid special data types in case the database needs to be ported to mysql or postgres, and so far I never had problems using the guids in nvarchar(36) or character(36).
Perhaps someone has some experience with this and can give some ideas?