On the way out (daily user here). I started a project about 4yrs ago, it was EF vs NH. Went with NH because EF was still pretty immature. The momentum is pret

On the way out (daily user here). I started a project about 4yrs ago, it was EF vs NH. Went with NH because EF was still pretty immature. The momentum is pretty clearly toward EF IMO. NH is missing a lot, including proper migration tooling and deep async support. But I don't think that's the real issue. The more foundational problem in my view, is that NH deeply assumes blocking/synchronous database access. I have no idea how NH lazy loading will ever work with async. I imagine you'll have a bunch of FK refs all marked Task<T> that will have to be awaited? In any case, my bet is that EF will get there a lot more quickly than NH.