Do you need a queue server for REST API?

Question

Message Queues

Good afternoon, I ask for advice from knowledgeable people.
The task is to implement your own API server, which will later use both a web application and a mobile application.
The implementation method is clear and all the tasks are clear, but I have never worked with queue servers and I don’t understand its expediency on a particular project
Please tell me, is it necessary to use a queue server for this kind of server? as there will be both mobile and web clients.
And another question: The queue server, if needed, does it act as an intermediary between my API and the client? or requests go to API links but there they are immediately accepted by the queue server?

Answer 1

Technically, the server does not care whose request to respond to: a web application or a mobile application. So 10 requests from the web app is like 5 requests from the web app + 5 requests from the mobile app.
In addition, the queue server is used for setting and distributing tasks, and not for balancing the load of the http server. Therefore, if you are worried about the load, then you need a balancer. But probably in this case a balancer is not needed either.

Answer 2

A queue server is needed in several cases:
1. If you need to send some content to many clients (for example, send a message to a group in messengers)
2. If you need to send a lot of content to clients that are constantly in standby mode (push notifications)
3. If you need to send any messages without worrying about delivery
Describe a bit the purpose of the applications and you will be told whether you need it or not