> > My question is why would the app use the load balancing, that should be > happening at the server end, not on the app side.
I'm no expert in the art of load balancing, that's for sure. I chose to use the client side as it seemed to require less resources than the server side, plus technically it's easy to understand. I've set up my own servers and am always nervous about doing something potentially dangerous and new so that's another reason I used the client side. Essentially, what I do for load balancing is to randomly select a server to use for the client session. That will guarantee (or just about) an even distribution of requests to the servers. It seems to work and I've used this method for years on web apps successfully. After we release the next version of our major app (coming in a week or so) and start earning some actual cash on the project, I may get a professional involved who knows all about that stuff and can setup a server side load balancing system that is bullet proof and hacker resistant. The next version sips at the server unlike the current version which gulps at it, so the problem will pretty much be solved with that release. We should be able to handle over 2,000,000 uses per day with the new version vs. about 500,000 with the current app without upgrading the infrastructure. -John Coryat -- You received this message because you are subscribed to the Google Groups "Android Discuss" group. To view this discussion on the web visit https://groups.google.com/d/msg/android-discuss/-/OHHbue-EkUkJ. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/android-discuss?hl=en.
