Performance loss on using united id?

public class RestauraceObjednavkaHeader : IEntity<string>
{
    // Primary key
    public required string Id { get; set; }
    
    // Before doing anything with the table, we always assume its status is Open
    public required Status Status { get; set; } = Status.Open;

    // Date and time of the order
    public required DateTime Datum { get; set; }

    // Navigation property | Restaurace_Objednavka_Header M:N User
    // We need to know who made the order
    public required ICollection<ApplicationUser> User { get; set; } = [];

    // Navigation property | Restaurace_Objednavka_Header 1:N Stul
    // We need to know which table the order is for
    public required ICollection<Stul> Stul { get; set; } = [];
}

public class RestauraceObjednavkaHeader : IEntity<string>
{
    // Primary key
    public required string Id { get; set; }
    
    // Before doing anything with the table, we always assume its status is Open
    public required Status Status { get; set; } = Status.Open;

    // Date and time of the order
    public required DateTime Datum { get; set; }

    // Navigation property | Restaurace_Objednavka_Header M:N User
    // We need to know who made the order
    public required ICollection<ApplicationUser> User { get; set; } = [];

    // Navigation property | Restaurace_Objednavka_Header 1:N Stul
    // We need to know which table the order is for
    public required ICollection<Stul> Stul { get; set; } = [];
}

using RestauraceNET8.Data.EF.DAL.Entities;
namespace RestauraceNET8.Data.EF.DAL.Mappers;

public interface IEntityMapper<in TEntity>
    where TEntity : IEntity<string>
{
    void MapToExistingEntity(TEntity existingEntity, TEntity newEntity);
}

using RestauraceNET8.Data.EF.DAL.Entities;
namespace RestauraceNET8.Data.EF.DAL.Mappers;

public interface IEntityMapper<in TEntity>
    where TEntity : IEntity<string>
{
    void MapToExistingEntity(TEntity existingEntity, TEntity newEntity);
}

You are correct. In a Blazor project, the Data Access Layer (DAL) should not depend on AutoMapper or similar libraries, as it should remain lightweight and focused on data operations. Instead, the Business Layer (BL) can utilize AutoMapper for mapping between entities and DTOs.

You are correct. In a Blazor project, the Data Access Layer (DAL) should not depend on AutoMapper or similar libraries, as it should remain lightweight and focused on data operations. Instead, the Business Layer (BL) can utilize AutoMapper for mapping between entities and DTOs.