Skip to main content

Main difference between Code First, Model First, Entities First

In one of my latests post I wrote about Hybrid Code First. When I started to write about it I realised that it is not very clear and transparent what does Code First, Database First and Model First are and what are differences between them.
The main scope of this post is to define in a few words each of this mechanisms and what are the main difference between them.
  • Code First - Define the domain first in code. Based on this domain, the database will be created on the fly by Entity Framework. This approach is used very often in combination with DDD (Domain Driven Development)
  • Database First -  Define the database schema first. Based on it, EF generates the code that maps the database to our entities and the access mechanism
  • Model First - Define the model in a design tool. Based on this design, EF will generate the entities and the database structure that is needed
Now, that we know what are the available mechanism to define and map our model, let's see what are the main characteristics of each of this mechanism. 

Code First 
  • Full control to the code
  • No code generated by tools of frameworks
  • DB schema doesn't need to be managed
  • Mapping can be done from the code directly using Fluent API
  • EF designers are not required
  • Changes to database schema will be lost (because the code defines the schema - Except when you are using Hybrid Code First)
  • DB creation is managed 100% by EF
  • No DB knowledge is required (until you have performance problems) 
Model First
  • A designer that can be used to define the model
  • Entities (using t4 template) and DB schema is generated automatically from this designer 
  • For custom POCO configuration or extensibility you will need to use partial classes or modify T4 template
  • No direct control the DB schema that is generated
  • No direct control of POCO entities that are generated 
  • Any change in DB schema will be lost or will cause an error in the EF, because DB is generated using the model defined in the designer
Database First
  • Full control at DB schema
  • Database can be created separately and POCO entities will be generated automatically
  • Existing database can be used without any kind of changes
  • Database schema can be changed without any kind of issues and the entities will be updated 
  • Any additional items on POCO entities will required partial classes or changes of T4 template

There is no best solution. Based on the needs and different context you will prefer to use a specific solution. For example, when you have an existing database you may prefer to use Database First. If you want to have full access to entities than you may prefer Code First.

Comments

Popular posts from this blog

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

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(

Azure AD and AWS Cognito side-by-side

In the last few weeks, I was involved in multiple opportunities on Microsoft Azure and Amazon, where we had to analyse AWS Cognito, Azure AD and other solutions that are available on the market. I decided to consolidate in one post all features and differences that I identified for both of them that we should need to take into account. Take into account that Azure AD is an identity and access management services well integrated with Microsoft stack. In comparison, AWS Cognito is just a user sign-up, sign-in and access control and nothing more. The focus is not on the main features, is more on small things that can make a difference when you want to decide where we want to store and manage our users.  This information might be useful in the future when we need to decide where we want to keep and manage our users.  Feature Azure AD (B2C, B2C) AWS Cognito Access token lifetime Default 1h – the value is configurable 1h – cannot be modified

What to do when you hit the throughput limits of Azure Storage (Blobs)

In this post we will talk about how we can detect when we hit a throughput limit of Azure Storage and what we can do in that moment. Context If we take a look on Scalability Targets of Azure Storage ( https://azure.microsoft.com/en-us/documentation/articles/storage-scalability-targets/ ) we will observe that the limits are prety high. But, based on our business logic we can end up at this limits. If you create a system that is hitted by a high number of device, you can hit easily the total number of requests rate that can be done on a Storage Account. This limits on Azure is 20.000 IOPS (entities or messages per second) where (and this is very important) the size of the request is 1KB. Normally, if you make a load tests where 20.000 clients will hit different blobs storages from the same Azure Storage Account, this limits can be reached. How we can detect this problem? From client, we can detect that this limits was reached based on the HTTP error code that is returned by HTTP