In the midst of developing an infrastructure to support a gaming platform that will cater to a large user base, performance is our top priority. We are striving to parallelize the architecture by running APIs, databases, and applications on separate servers for horizontal scalability.
The biggest challenge we're facing lies in one particular application - a web app. This app requires access to models from our centralized API, but encounters issues with the same origin policy on older browsers.
While mobile clients have no trouble connecting, web browsers struggle due to limited CORS support for certain HTTP verbs like PUT and DELETE. Our proposed workarounds involve either rewriting the API for more abstraction (which may impact development time and performance) or utilizing JSONP for POST requests, potentially adding latency through a proxy.
Ultimately, we need to determine if these options are our only choices or if there are alternative solutions worth exploring. Which approach would best suit a gaming platform like ours?