Do I have to worry about HTTP overhead when calling local web services?

Question

I am currently processing a fairly large-scale PHP web application. Part of this redevelopment involves moving the bulk of a fairly healthy business logic from the core of a web application and moving it to a set of SOAP web services.

What currently concerns me (a little) is perceived as overhead, this leads to this in terms of local HTTP traffic. I must explain that SOAP web services will now be on the same physical server for the foreseeable future, and if and when they move, they will remain on the same network. I'm interested in the fact that for every call that is an internal call to the php function, now the HTTP request calls a similar function call.

Obviously, this is something that I can measure as I move along the line, but I was wondering if anyone could offer any advice or, more importantly, share any previous experience with receiving the application on this route.

Answer 1

Do you make hundreds or thousands of these calls per second? If not, then you probably won't have to worry.

But the profile. Set up a prototype of a networked system with a lot of SOAP calls and see if it slows down to unacceptable levels.

Answer 2

, . ( ) - .

- SOAP, HTTP, , , "-" (, ). , SOAP, , , HTTP, , , PHP-, .

, php , - API-.

Answer 3

- SOAP? , ?

, HTTP-, , /- / XML "" - "" - . =)

- SOAP, .

@Skilldrick - , HTTP-.

, , ..

Answer 4

SOAP is more verbose than REST. REST uses HTTP to do the same with less network bandwidth if that is your problem.

Cm:

• WhatIsREST
• Wikipedia

To really answer your question, remember the 80/20 rule . To do this, use the comparison / tracing tool to help you find where your hot spots are. Correct them and forget about the rest.