title: Is Data Reader better or Data Set for application where we may have Concurrency issue
body: <p>I know the difference between Data Reader and Data Set.</p>
  
  <p>The DataReader is a better choice for applications that require optimized read-only, fast and forward-only data access.</p>
  
  <p>The Data set is better for Application wherein you can get all the data and update it according to your needs at application level and submit the change to the database.</p>
  
  <p>Please clear if there is anything wrong in my understanding.</p>
  
  <p>Now I had an interview there a person asked me. Is datareader or Connected architecture good for application like ticketing system. Basically she meant were many user might be trying to update the same table. Thus the concept of Concurrency comes.</p>
  
  <p>We can Use Disconnected architecture to check for concurrency and let only one user update the table at a time. But dont know how it happens in terms of connected Architecture. Does the connection to the data base and particularly to the table concerned would that make only one user do the update while others who try to hit later wont be able to do that.</p>
  
  <p>Wont it affect the performance if all the user have opened a connection as database will reach bottle neck.</p>
  
  <p>I hope i will get the answer to understand them.</p>