title: Understanding REST in terms of scalability, performance,
body: <p>I just want to know if my thoughts concerning REST are right. Let's imagine we have a shopping site. With a conventional approach the shopping cart would be stored in the users session so that the server has to manage many items for user( User#1: item1, item2, item3; User#2: itemA,itemB, item3,...). So the server has to have lots of memory/computing power if there are more than a thousand users browsing on the site and adding items to their shopping cart.</p>
  
  <p>In a REST approach there is no session, so the client has all information about the items in the shopping cart. This means that the server doesn't need to have such big memory requirements and I can easily scale this. </p>
  
  <p>Now if I add an item in the non-REST-approach to the shopping cart it would go directly into the session. On the other hand, if I add an item in the REST-approach, I have to update the entity in the database (/shoppingcart/1234/) and this would take a bit longer since I have to go one level deeper (client->server->database). </p>
  
  <p>Is this correct so far or am I missing or misunderstanding a point?</p>