Upgrade your account to a Community Supporter account and remove most of the site ads.

Reply to thread

Message: <blockquote data-quote="AbdulAlhazred" data-source="post: 5485227" data-attributes="member: 82106">Yes, and then in either case every time you want to deploy a client to another device you have reproduce and maintain all the 'business' logic yet again so you end up with a C# version, an HTML5/JS version, an Objective C version, and potentially a Java version as well... Yes, designing your client to be mostly a very dumb thin UI with most of the logic on the backend probably makes things somewhat slower in some cases, but it also means that in the long run your architecture is a lot more robust and you can at least potentially afford to support more different clients. It also has positive implications for other services. For instance it is a lot easier for something like a VTT to leverage a backend service that knows how to do most of the calculations related to characters for it. Really sluggishness due to implementing logic in the back end and doing a fair number of round trips is not really related to delays in round-tripping either. It isn't going to take more than a couple hundred milliseconds to round trip a request to the server. The delay would be in back end processing time. Nominally it isn't any slower to do the processing there than on the front end. It is really a load issue. The key point being that can be solved by throwing enough infrastructure at it and setting it up properly. Something like OCB back end should be pretty simply to scale horizontally, you can just create more instances and load balance.</blockquote>

Verification