I'm not totally sure what's the microservices architecture better approach. Since I have to build this backend API's transporting messages to microservices using an AMQP broker in the middle, I'm using Django REST to decorate endpoints, send the messages to the broker, handling authentication and dispatching only HTTP responses if I have successfully sent a message. My particular concerns are about:
Do I need to develop a subscriber/consumer for any API endpoint I'm developing? I mean, I want to send the response corresponding to the requested data.
My other concern is about subscribers, I've developed before a messaging backend, but the difference on that project was that the clients were receiving data through websockets, that I think it's a better approach dealing with microservices responses instead HTTP responses and payload.
How are you dealing with responses and timeouts serving to HTTP consumers?
Do I need to develop a subscriber/consumer for any API endpoint I'm developing? I mean, I want to send the response corresponding to the requested data.
My other concern is about subscribers, I've developed before a messaging backend, but the difference on that project was that the clients were receiving data through websockets, that I think it's a better approach dealing with microservices responses instead HTTP responses and payload.
How are you dealing with responses and timeouts serving to HTTP consumers?
Sorry If I'm not being very clear.