Скачать с ютуб Learn To Love DDD-Style Strongly Typed IDs в хорошем качестве

Learn To Love DDD-Style Strongly Typed IDs

Become a sponsor to access source code ►   / zoranhorvat   Join Discord server with topics on C# ► https://codinghelmet.com/go/discord Enroll course Beginning Object-Oriented Programming with C# ► https://codinghelmet.com/go/beginning... Subscribe ►    / @zoran-horvat   There are many implementations of strongly typed ID types on the Internet, but not many satisfy all of the mandatory and nice-to-have traits we expect from such a class. An ID, custom or built-in, must be an immutable value object with full value-typed semantics, supported by the underlying database and the intermediaries such as ORMs and micro-ORMs; it would be nice if it caused no additional allocations and garbage collection overhead. This video will help you understand the steps required to design a small but powerful custom ID type that satisfies all functional and performance considerations that define a good identity. An identity is essential to any object we persist. It spans the time between application runs and the time between creation and a later retrieval of the same persisted object. Hence, it exists in all persisted entities. In this video, we start with autoincrement IDs and GUIDs, finding their ultimate deficiency - an ability to generate application bugs. Then, we introduce strongly-typed custom IDs that are application-generated and backed by compile-time assignment checks. Before this short video ends, you will learn to love the simplicity, safety, and even speed of your custom identity types that are powerful, compile-time safe, and fully supported by Entity Framework Core and relational databases. 00:00 Intro 01:15 Autoincrement and GUID IDs 02:54 The Failure Caused by Using GUIDs 04:53 Developing a Custom ID Type 08:53 Outro Thank you so much for watching! Please like, comment & share this video as it helps me a ton!! Don't forget to subscribe to my channel for more amazing videos and make sure to hit the bell icon to never miss any updates.🔥❤️ ✅🔔 Become a patron ►   / zoranhorvat   ✅🔔 Subscribe ►    / @zoran-horvat   ⭐ Learn more from video courses: Beginning Object-oriented Programming with C# ► https://codinghelmet.com/go/beginning... ⭐ Collections and Generics in C# ► https://codinghelmet.com/go/collectio... ⭐ Making Your C# Code More Object-oriented ► https://codinghelmet.com/go/making-yo... ▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬ ⭐ CONNECT WITH ME 📱👨 🌐Become a patron ►   / zoranhorvat   🌐Buy me a Coffee ► https://ko-fi.com/zoranhorvat 🗳 Pluralsight Courses ► https://codinghelmet.com/go/pluralsight 📸 Udemy Courses ► https://codinghelmet.com/go/udemy 📸 Join me on Twitter ►   / zoranh75   🌐 Read my Articles ► https://codinghelmet.com/articles 📸 Join me on LinkedIn ►   / zoran-horvat   ▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬ 👨 About Me 👨 Hi, I’m Zoran, I have more than 20 years of experience as a software developer, architect, team lead, and more. I have been programming in C# since its inception in the early 2000s. Since 2017 I have started publishing professional video courses at Pluralsight and Udemy and by this point, there are over 100 hours of the highest-quality videos you can watch on those platforms. On my YouTube channel, you can find shorter video forms focused on clarifying practical issues in coding, design, and architecture of .NET applications.❤️ ▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬ ⚡️RIGHT NOTICE: The Copyright Laws of the United States recognize a “fair use” of copyrighted content. Section 107 of the U.S. Copyright Act states: “Notwithstanding the provisions of sections 106 and 106A, the fair use of a copyrighted work, including such use by reproduction in copies or phono records or by any other means specified by that section, for purposes such as criticism, comment, news reporting, teaching (including multiple copies for classroom use), scholarship, or research, is not an infringement of copyright." This video and our youtube channel, in general, may contain certain copyrighted works that were not specifically authorized to be used by the copyright holder(s), but which we believe in good faith are protected by federal law and the Fair use doctrine for one or more of the reasons noted above. #csharp #dotnet #ddd