Working with a remote web service. How to do it properly?

Good day!

This: the service is data which can give data through your API. Data is not static.

Problem: we do third-party app which has to show different selections of the user. The collections are displayed and updated in real time.

Do I understand correctly that in this scheme we need to have a backend written in, say, PHP. And the user interface is written in JS.

Accordingly, the user selects what he wants to, JS makes a request to our backend, the backend sets the authorized server connection data and outputs them to the client.


Questions: we don't "get" if you make a backend in PHP? No problems with the scheme that I gave? With the requirement to maintain connectivity.
Perhaps the scheme has some mistakes?
Thank you.
July 9th 19 at 13:23
2 answers
July 9th 19 at 13:25
If things are really as you describe, it will get you there better node.js fit
July 9th 19 at 13:27
Generally the limit on the number of requests per second, minute, day. Never heard of a limit on the number of connections. So I think a permanent connection here is not necessary.

As the limit is, the data retrieved from the api is stored on your server. When repeated requests not to ask the api the same.
The data on the remote server, so to speak, constantly being updated and modified. - keyon.Reichel commented on July 9th 19 at 13:30

Find more questions by tags APIPHPWeb Development