title: MVC Web Api as a middle tier service
body: <p>In our recent application we are planning to use MVC Web API as a Middler tier service. Meaning, front end will access the WebAPI middler tier service to get all the data it required from DB and to update the data back to DB. Along with this there may be many other methods that we will need. For example check whether user already exists in the system, Validate the address, etc. Now I have come into a point that my webapiconfig.cs routing is becoming more complex. For example my UserController in WebApi project will have following methods.</p>
  
  <blockquote>
    <p>public User Get(int userId)
            {
            }</p>
  </blockquote>
  
  <pre><code>    public bool IsUserExists(string username)
      {
      }
  
      public bool UpdateUser([FromBody]User user)
      {
      }
  
      public bool ChangePassword(string username, string password)
      {
      }
  </code></pre>
  
  <p>To manage all of these I may need so many routing configurations in webapiconfig.cs. I am not sure how to deal with these when other controllers comes to the picture. Should I use AttributeRouting? Any suggestion highly appreciated. Thanks.</p>