The following are some advantages of statelessness:

• As the server does not need to manage any session, deploying the services to any number of servers is possible, and so scalability will never be a problem
• No states equals less complexity; no session (state) synchronize logic to handle at the server side
• As the service calls (requests) can be cached by the underlying application, the statelessness constraint brings down the server's response time, that is, it improves performance with regard to response time
• Seamless integration/implementation with HTTP protocols is possible as HTTP is itself a stateless protocol
• Improves visibility as each request is its own resource and can be treated as an independent request
• Improves reliability as it can recover from partial failures

The following are some disadvantages of statelessness:

• Increase per-interaction overhead
• Each request of webservices needs to get additional information so that it get parsed (interpreted) so that the server understands the client state from the incoming request and takes care of the client / server sessions if needed