The obvious solution is probably the best: Use an asynchronous framework (like node.js or asyncio) for the REST interface and wait for the completion of the task to return a response.<p>That process wouldn&#x27;t handle all the details of the task, but it can wait for notification of the task via other means (celery, rabbitmq, redis, whatever...).<p>Personally I think REST is the best paradigm for most microservices. There is one exception: Data streams are inherently stateful and some kind of websocket&#x2F;message passing is a lot more useful in that case.