title: Web API integrated with Entity framework 5 with database first approach
body: <p>I have followed below steps</p>
  
  <ol>
  <li>Created a new C# solution in VS 2012</li>
  <li>Added a c# class Library project for creating Model from existing Database</li>
  <li>Added a new EDMX file off of an existing database to above project</li>
  <li>Built the project succesfully</li>
  <li>added new C# Class library project for creating a repository class </li>
  <li>Added a reference to Library project created in the step 1</li>
  <li>Added a new class "XyzRepository" that has CRUD operations (written in L2E) required for web service methods</li>
  <li>Built successfully</li>
  <li>Created a new MVC 4 project of type WebAPI template and addded a ApiController</li>
  <li>Inside the Api Controller Created a HttpPost method "UpdateStatus" with return type   HttpResponseMessage</li>
  <li>Instantiated XyzRepository and invoked  _respository.UpdateStatus a bollean return type method</li>
  <li>Constructed response using Content = new StringContent("");</li>
  <li>Returned response </li>
  <li>Consumed WebAPI using HttpClient from another MVC 4 project of type Internet Application template.</li>
  <li>Ran the MVC 4  page to see the result and everything works fine.</li>
  </ol>
  
  <p>Now the question </p>
  
  <p>I have seen tonnes of discussions in several forums where Web API is integrated with repository patterns that interacts with POCO classes with code first approach. This approach uses IoC, DI and DatabaseCreation when model changes and so on. </p>
  
  <p>Since i have a existing database i used Database First approach. But I am not entirely sure if my design has any flaws drawbacks in terms of concurrency, performance etc. Since all examples used code first approach that makes me nervous.</p>
  
  <p>I wanted to hear opinions from experts so I don't get surprised later in the cycle.</p>