title: Should HTTP Based Micro Services always be Rest
body: <p>I'm currently developing a micro service that basically provides calculation services to other micro services. It does not store data or have any resources like a sales order. It only calls other micro services and then calculates metrics and prices to return a result.</p>
  
  <p>I'm kind of struggling  trying to make a rest API with resources names that are nouns when all I do is calculate stuff and return results (more like an action).</p>
  
  <p>So can we have a micro services that behaves more like an HTTP API than a Restful service (is it a bad practice, an anti pattern , an architecture smell, ....)</p>
  
  <p>Regards</p>