title: Is it still ok to use Linq-to-Sql
body: <p>When Linq-to-Sql was first released, I used it quite a lot for small and medium sized projects where a true multi-tier architecture wasn't required.</p>
  
  <h2>NHibernate, Small Middleware, Overkill</h2>
  
  <p>Where I work, we now almost exclusively use NHibernate for true Domain Driven development.</p>
  
  <p>I'm working on a small temporary (a lifetime of probably a year, maybe less) middleware component where NHibernate feels slightly overkill in terms of configuration and keeping the entities up to date. Especially because I haven't got any control over the DB, it sometimes changes, and it's a little bit "legacy".</p>
  
  <p>Some changes were recently made to the DB, and the NHibernate mappings are not very complete.</p>
  
  <h2>Linq-to-Sql? Or EF?</h2>
  
  <p>I thought it might be easier just to rip out the IRepository implementation I have and replace it with a Linq-to-Sql implementation. Then I can just use lambdas for my simple queries, and just drag and drop the tables in.</p>
  
  <h2>RAD But Dead?</h2>
  
  <p>In this scenario the RAD elements of Linq-to-Sql make sense. But it's essentially old technology. Should I not use it? I've never used the Entity Framework. Should I use that, is it as easy and quick to use?</p>
  
  <p>cheers</p>