Problems with performance optimization of PHP business interface in SOA?

Question

• The performance of writing business interfaces in modules is very slow, and one block will appear from time to time until it times out

• In the development environment, ordinary interfaces generally take 150ms, but interfaces called across modules will exceed 1000ms and are unstable

• Later, public interfaces (such as session, token) were written as in-function calls so that there would be no timeout, but the performance was still very slow

May I ask if you have any optimization methods or points to pay attention to when calling PHP cross-module interfaces?

Answer 1

Use rpc calls between internal applications to support concurrent calls. . . . As for the slow interface call you mentioned, you still need to locate the cause first and record the program running time, so that you can know whether it is caused by internal problems in the program or external factors. . . The development environment is not fast 150ms

Answer 2

If you use SOA architecture, you must set a timeout for each interface when calling the interface. The interface provided by PHP should be stress tested to see how much concurrency is supported. Look at qps and judge whether the interface response time is normal based on the average response time of the interface. If not, Normally, you need to review the code to analyze the bottleneck