I need help with my current setup where I have a .NET backend running on ASP.NET and want to use PHP for the frontend development. My team will include myself plus a couple of PHP developers.
Right now I’m using XML-RPC to make these two systems talk to each other. Both PHP and .NET can handle XML-RPC pretty well, and I built the backend part myself. But I’m running into some problems.
The main issues are that XML-RPC doesn’t have built-in security features for user authentication. Also, the performance isn’t great because converting objects to XML and back takes too much time.
Has anyone dealt with similar architecture challenges? What other options should I consider for connecting PHP frontend with .NET backend? I’m looking for something faster and more secure than XML-RPC.
xml-rpc is pretty outdated now. why not just use http calls with json instead? way less overhead since you don’t have to parse xml, and you can handle auth with oauth or api keys. i’ve built similar stuff and keeping it simple always beats getting fancy with old protocols.
Switch from XML-RPC to REST APIs with JSON - it’ll massively improve your PHP and .NET integration. I saw huge performance gains because JSON parsing destroys XML serialization speed-wise. For security, JWT tokens give you stateless auth without dealing with session headaches. .NET Web API makes building RESTful endpoints dead simple, and PHP handles JSON natively so data consumption is smooth. Want flexible queries? Check out GraphQL, but it adds complexity. Bottom line: REST gives you lighter payloads and better caching, which should fix your performance problems.
Hey! What’s your current XML-RPC load looking like - how many requests per second before it starts choking? Have you looked into gRPC? Might be overkill but it absolutely destroys XML serialization performance-wise. What kind of data are you moving between systems?