title: EJB3 Remote vs Webservices, performances?
body: <p>I'm planning to a webapp where every guy using it would have a client that would run computations on its computer (because these computations can't be done on the server, too much load...), and then send results to the server.</p>
  
  <p>I guess there will be lot of people interested in my application and that's why i'm wonder if my architecture is good and if i'll be able to handle thousands of people.</p>
  
  <p>I'm planning to expose remote EJB through JNDI with Glassfish server, so 1000 people could use these EJB at the same time (i guess there could be 5-50 requests / second) to retrieve the data needed for local computation, and then to send the results...</p>
  
  <p>Is it expensive to expose EJB to many clients?
  Would it be better to use webservices, rmi, another solution?</p>
  
  <p>Would you recommend me another architecture for what i'm going to do?</p>