Skip to main content

Entity Framework - Hybrid Code First

By
Let's talk about an interesting subject related to Entity Framework (EF). When you are using EF there are different mechanism to map your model:
  • Code First - we write the code first and the DB is generated automatically based on the code
  • Database First - we define the DB structure and POCO entities are created automatically
  • Model First - we design the model in a 'nice' designer. This designer will generate the classes and the database model
All of them are perfect and works great. Based on our needs, preferences and team skills we can decide to go with an approach or another, but in the end we will end up with the same thing. I will follow up later on with a different post where I will compare them.

Now, let's talk about different scenarios that is used by people. I saw in a lot of implementation where people are afraid of Code First or Model First. Because of this I realize that most of them are using a hybrid solution that I called Hybrid Code First.

Why I called Hybrid Code First? 
Well, people don't trust EF to generate the database schema. Because of this they are defining the model in the code as classes (POCO). Once this is done, they are defining the database schema - tables, indexes, keys, the relationship between entities. 
Once this step is done, they are defining the mapping between their classes (POCO) and database schema using Fluent API. In this way they are connecting each C# entity model to each table, column or key.

Is this a good approach?
Well...there is no the right answer. This approach it is used because people don't trust EF enough. People don't trust that EF can generate a database schema good enough. Based on this fears they combine Code First with Database First using Fluent API. 
This way they have full control to database schema and also to the model (C# entities). 
Of course, because of this versioning needs to be made manually, but they don't trust out of the box versioning of Code First, even if with EF 4.1 version, it works pretty great.

This is another approach to define and manage the entities model. Even if it is more time consuming, it offers a safety nest for developing team. Offering them control for both part (DB and Code).  
Labels:

Comments

  1. tudor_turcuJune 11, 2015 at 7:21 PM

    We are using exactly this model - and not because we don't trust EF to generate the database create/update scripts - it's because very often the DB schema can't be inferred only from the mappings.

    An example:
    - all C# classes are mapped to database views, that perform (custom) queries over the DB tables - how could EF by itself generate such a database? :)

    ReplyDelete

Post a Comment

Popular posts from this blog

Windows Docker Containers can make WIN32 API calls, use COM and ASP.NET WebForms

By
After the last post , I received two interesting questions related to Docker and Windows. People were interested if we do Win32 API calls from a Docker container and if there is support for COM. WIN32 Support To test calls to WIN32 API, let’s try to populate SYSTEM_INFO class. [StructLayout(LayoutKind.Sequential)] public struct SYSTEM_INFO { public uint dwOemId; public uint dwPageSize; public uint lpMinimumApplicationAddress; public uint lpMaximumApplicationAddress; public uint dwActiveProcessorMask; public uint dwNumberOfProcessors; public uint dwProcessorType; public uint dwAllocationGranularity; public uint dwProcessorLevel; public uint dwProcessorRevision; } ... [DllImport("kernel32")] static extern void GetSystemInfo(ref SYSTEM_INFO pSI); ... SYSTEM_INFO pSI = new SYSTEM_INFO(
Post a Comment
Read more

ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded

By
Today blog post will be started with the following error when running DB tests on the CI machine: threw exception: System.InvalidOperationException: The Entity Framework provider type 'System.Data.Entity.SqlServer.SqlProviderServices, EntityFramework.SqlServer' registered in the application config file for the ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded. Make sure that the assembly-qualified name is used and that the assembly is available to the running application. See http://go.microsoft.com/fwlink/?LinkId=260882 for more information. at System.Data.Entity.Infrastructure.DependencyResolution.ProviderServicesFactory.GetInstance(String providerTypeName, String providerInvariantName) This error happened only on the Continuous Integration machine. On the devs machines, everything has fine. The classic problem – on my machine it’s working. The CI has the following configuration: TeamCity .NET 4.51 EF 6.0.2 VS2013 It see
8 comments
Read more

Navigating Cloud Strategy after Azure Central US Region Outage

By
 Looking back, July 19, 2024, was challenging for customers using Microsoft Azure or Windows machines. Two major outages affected customers using CrowdStrike Falcon or Microsoft Azure computation resources in the Central US. These two outages affected many people and put many businesses on pause for a few hours or even days. The overlap of these two issues was a nightmare for travellers. In addition to blue screens in the airport terminals, they could not get additional information from the airport website, airline personnel, or the support line because they were affected by the outage in the Central US region or the CrowdStrike outage.   But what happened in reality? A faulty CrowdStrike update affected Windows computers globally, from airports and healthcare to small businesses, affecting over 8.5m computers. Even if the Falson Sensor software defect was identified and a fix deployed shortly after, the recovery took longer. In parallel with CrowdStrike, Microsoft provided a too
Post a Comment
Read more