Stop Using Records As Strongly Typed IDs!

Strongly typed IDs is a very important concept, inspired from DDD. The main purpose is to eliminate primitives obsession, to give our code a better intent and to avoid misplacing identifiers. But what about performance? Virtually everybody talks about C# records as ideal for this purpose. But can we do better in terms of performance?
#dotnet #softwarearchitecture #ddd #software

Join this channel to get source code access and other perks:
   / @codewrinkles  

Also follow me here (especially if you are a self taught developer):
✅My other channel:    / @danpatrascutech  
✅Facebook:   / danpatrascutech  
✅Instagram:   / danpatrascutech  
✅TikTok:   / danpatrascutech  
✅Newsletter: https://www.danpatrascu.tech/

Milan's video:    • How Strongly Typed IDs Can Make Your ...  
Amichai's video:    • The Identity Paradox | DDD, EF Core &...  

Content:
1. Intro: 00:00
2. Implementing strongly typed IDs: 01:21
3. Initial benchmark: 03:00
4. What if we use structs? 04:50
5. What if we use regular class? 07:21
6. How we explain this? 08:23
7. Don't use records! 09:24

My setup:
Camera - Canon EOS M50 Mark II: https://amzn.to/3SJxS4d
Lav mic - Rode Lavalier GO Professional: https://amzn.to/3mmZS1B
Condenser mic - Shure SM7B: https://amzn.to/3JaqjQN
Audio console - Rodecaster PRO II: https://amzn.to/3KTVMIg
Laptop - Dell Latitude: https://amzn.to/3KV4SEW
Monitors - Benq 27 inch: https://amzn.to/3JbM6aU
Lights - 2x Godox SL-60W: https://amzn.to/3KV3qCj