Asad Awadia At work we're using vert.x for a REST API that offloads processing requests to Kafka and acknowledges clients.

It really depends on the use case. If it is IO intensive, I'd go with something reactive, e.g. ExpressJs on Node, SpringWebFlux or may be even Vertx If it is compute intensive, go with something made to handle CPU intensive tasks, you can consider Spring or Python, Go etc Sometimes it also depends on how fast you can get it up and running. Those times I'd always go with something the team is familiar with and what is easy to setup ( for me its usually Nodejs )

This is really cool !! If you write about how you made it, it'd be great.

Hey Syed, having trouble opening the post in Edit mode. The page crashes.

Thanks for this! I'll try retaining node_modules between builds with progress=false

Built a very simple chat application to get started on socket.io Source Demo

We have built something in-house for managing tenant configurations very similar to what you have described. It does layering and overrides, and there's a client that attaches to applications and picks up config changes dynamically. So no restarts are required when you change configurations. I've been looking for out of the box solutions for the same and found Spring Cloud Config. Check it out. https://cloud.spring.io/spring-cloud-config/