Scalability? Is this a viable use of EasyXDM?

[FutureForward]

I am hoping to use EasyXDM in this way, I have a web app and want it
to send data (a string) to my server for processing, and have it sent
back to the customer for use with their product. The reason I am doing
this is as a way to offer a 30 day trial, and also to track the URLs
of the people that are using the app.

I have it implemented and it is working well.

My question is about scalability. Every time someone hits save changes
in the web app, it sends data to the same file on my server
process.php, which uses JSON to return the processed data.

If my product is successful, and say, thousands of users are acting at
the same time, will my process.php file get overloaded? Should I host
different versions of process.php on different servers, so that if one
server goes down, only a portion of my customers are affected?

Any insight is appreciated.

[Øyvind Sean Kinsey]

I'm not seeing what your question has to do with easyXDM - these are two orthogonal things.

One is a means of providing XDM, the other is how to scale a server side application.

Allthough I deal with both, this forum is really just targeted at the first.

[FutureForward]

I guess perhaps it doesn't.

I am using easyXDM to send data from a server side app on the client
side to a php file on the company server for processing, which is sent
back to the client. It is doing so reliably.

Just curious if there were any issues vis a vis scaling this up to
production that I need to be concerned about. I will look into scaling
a server side app.

Thanks!

[Øyvind Sean Kinsey]

When it comes to the XDM part, there is no real scale as the execution is always localized to a single client, and more client executing the code does not constitute higher load on any single component (except for the server serving the resources).

If it 'scales'? Hold on a sec and I'll ask my friends at Twitter or LinkedIn ;)