title: SOAP/REST Web Services - Infrastructure & Best Practices
body: <p>I have got my first job/responsibility to design and implement a web service (java, spring) from scratch to be consumed by external systems (other companies). I am excited about the opportunity, but at the same time since this is my first attempt, I want to make sure that I give my best...
  I am sure I have to consider the following as I evolve with the design :
  1. Scalability &amp; Minimal Latency
  2. SLA adherence (for e.g. 2 seconds for end to end)
  3. Supporting different Media Types (SOAP, POX, JSON)</p>
  
  <p>We are currently in the phase of defining the contract and while we are doing so, I would want to make sure that besides the application level details that I can take care of myself, I should also be able to consider the infrastructural challenges (Servers, Scalability etc.). </p>
  
  <p>I am looking forward to get some help in this regard if you can either answer based on your past experiences or point to to some resources that would help me move forward.</p>
  
  <p>P.S. :- I am already aware of the factors related to security, defining the policies in the wsdl, and other application level considerations. My main concern is on the choices and the decisions at the infrastructure level.</p>
  
  <p>Thanks!</p>