title: MVVM to interact with a web-service in a 3-tiered application
body: <h1>Question:</h1>
  <p>Does it make sense to use MVVM for a UI that interacts with a web-service in a 3-tiered application?</p>
  <hr />
  <h1>Details:</h1>
  <ol>
  <li><p>Application's architecture is 3-tiered:</p>
  <p><code>Presentation Layer &lt;--Web-Service--&gt;| Business Layer | Data Access Layer</code></p>
  </li>
  <li><p>Front-end: <em>.NET (WPF and C#)</em></p>
  </li>
  <li><p>Back-end: <em>Java EE</em></p>
  </li>
  </ol>
  <h2>Does it make sense to use MVVM for the UI?</h2>
  <ol>
  <li>How can the <strong>Model abstract the database</strong> since it cannot access it directly without the web-service in between?</li>
  <li>If it was in fact possible to abstract the database via the Model, is it even a <strong>good idea</strong> to do it that way?</li>
  </ol>
  <hr />
  <h1>Other considerations:</h1>
  <p><strong>Don't need to have a live update of data:</strong></p>
  <ul>
  <li><p>Updates on the DB needn't be instantly reflected on the UI and vice versa.</p>
  </li>
  <li><p>This makes me think that I don't need to have a Model as such. Is MVVM appropriate in my case?</p>
  </li>
  </ul>
  <hr />
  <p><strong>EDIT</strong></p>
  <h1>Links:</h1>
  <p>It'll help if you can post links to projects that have <strong>used an MVVM</strong> for a UI in a 3-tiered application.</p>