title: Is instantiating a GUID in Entity Framework Core bad practice?
body: <p>If I have a model with a key of type <code>Guid</code>, is it bad practise to set the ID explicitly in the constructor?</p>
  
  <p>I know it will be set implicitly by Entity Framework, but will anything bad happen (perhaps performance wise) from setting it explicitly?</p>
  
  <p>Example:</p>
  
  <pre><code>class MyModel
  {
      public MyModel()
      {
          Id = Guid.NewGuid();
      }
  
      [Key]
      public Guid Id { get; set; }
  }
  </code></pre>
  
  <p>I'm thinking a <code>Guid</code> is backed up by a sequential ID in SQL server, and if I set a value explicitly, I suppose I will decrease indexing performance because it will no longer be sequential?</p>
  
  <p>I have not been able to find an answer on this and I am highly curious about it.</p>