Aya Ragab on LinkedIn: #dotnet #microservices #softwaredevelopment #architecture #learning… | 12 comments (2024)

New Week .. New Achievement 🚀 Just Completed "Entity Framework Core in Action" Book! 📚💡 Key Takeaways:In this enriching journey, I've not only covered the fundamental concepts of Entity Framework Core but have also delved into advanced topics, empowering developers with actionable insights. Here are some key learnings I'm thrilled to share:1️⃣ **Mastering EF Core Fundamentals:** From entity relationships to data modeling, laying a solid foundation for understanding EF Core's core concepts.2️⃣ **Efficient Querying with LINQ and Fluent API:** Unveiling the power of LINQ and Fluent API to streamline data retrieval and manipulation.3️⃣ **Seamless Database Migrations:** Navigating the intricacies of migrations, ensuring a smooth evolution of database schemas.4️⃣ **Performance Tuning and Optimization:** Strategies and techniques to fine-tune performance, making applications faster and more efficient.5️⃣ **Integration with ASP.NET Core:** Exploring the seamless integration of EF Core with ASP.NET Core, creating robust and scalable applications.📘 This book isn't just a collection of concepts; it's a practical guide filled with real-world examples and best practices drawn from hands-on experience. #EntityFrameworkCore #LearningJourney #EFCoreInAction

85

4 Comments

I am excited to share my latest learnings in database design with Entity Framework Core! 💼📊In the ever-evolving world of software development, optimizing database structures is crucial for application performance. Today, I'd like to delve into a few strategies that Entity Framework Core (EF Core) offers for mapping inheritance hierarchies to database tables: Table Per Hierarchy (TPH), Table Per Type (TPT), and Table Splitting.1. *Table Per Hierarchy (TPH):* With TPH, EF Core maps all derived types of an inheritance hierarchy to a single database table. This can be a great choice when the derived types share many common properties and relationships. It's efficient in terms of storage but might introduce nullable columns for properties specific to derived types.2. *Table Per Type (TPT):* TPT involves mapping each type in an inheritance hierarchy to its database table. This approach ensures a clean, normalized schema and eliminates nullable columns. However, it may lead to more complex queries due to joins when querying related data from multiple derived types.3. *Table Splitting:* Table splitting is an interesting option that allows you to map multiple entity types to different parts of the same database table. This is beneficial when you have closely related entities that share some columns and have unique properties. It simplifies the schema while maintaining clarity.When deciding between these strategies, your application's specific requirements, such as performance, maintainability, and scalability, must be considered. Each approach has its pros and cons, so choosing the right one requires a deep understanding of your data model.Have you worked with TPH, TPT, or table splitting in EF Core? Share your thoughts and experiences in the comments below! Let's spark a conversation and learn from each other's database design journeys. 🚀💬 #EntityFrameworkCore #DatabaseDesign #SoftwareDevelopment #EFCore #InheritanceMapping #TablePerHierarchy #TablePerType #TableSplitting #LinkedInLearning

21