title: Why is ASP.NET Identity 2.0 using a GUID/string as user id?
body: <p>As the title says, I wonder, why ASP.NET Identity 2.0 uses a string with a GUID as primary clustered key for the user table. Does this have any advantages to an integer id? I see only the problem, that a GUID isn't the best choice for a clustered index.</p>
  
  <p>Am I missing anything or is a integer still the better choice?</p>