Understanding of url requests and responses to json data and stress testing of interfaces

It turns out that the request is just an address, which is usually obtained by GET. Instead of sending the json packet, the server returns the json packet. After the developer receives it, the json packet is parsed. (the phrase "requested a json packet" really made me misunderstand for a long time. In fact, the thing in BS or CS architecture is a round trip, request and response. Generally speaking, the interface (including parameters + address, etc.) is a request. After the correct request, the server will return a bunch of packets. This process is called response, and the packets are usually json packets. Parsing the json packets and arranging the front-end tags, you can see a pile of pictures and text messages on the interface. Anyway, I finally got it from get! Then the performance tester has to pay attention to the request and response (whether there is any or not), and don't pay too much attention to whether the data returned is correct (so it becomes a functional test). This is the interface test, and then the performance testing tool will script the interface under a certain scenario, and send it to the server to cause pressure, and the point to be tested is the stress test.