title: Deciding between TCP connection V/s web socket
body: <p>We are developing a browser extension which would send all the URLs visited by a logged in user to backend APIs to be persisted.</p>
  <p>Now as number of requests send to backend API would be huge and hence we are confused between if we create a persistent connection via websocket OR do it via TCP connection i.e. using HTTP rest API calls.</p>
  <p>The data post to backend API doesn't need to be real time as we anyway would be using that data in our models which doesn't demand them to be real time.</p>
  <p>We are inclined towards HTTP rest API calls as due to below reasons</p>
  <ul>
  <li>Easy to implement</li>
  <li>Easy to scale(using auto-scaling techniques)</li>
  <li>Everyone in the team is already comfortable with the rest APIs</li>
  </ul>
  <p>But at the same time cons would be</p>
  <ul>
  <li>On the scale where we would have a lot of post requests going to server not sure it would be optimised</li>
  <li>Feels like websockets can give us an optimised infrastructure :(</li>
  </ul>
  <p>I would love if I can hear from community if we can have any pitfalls going with rest API calls option.</p>