I'm pretty sure there's websocket (and related tech) support for your stack. I would explore this first. If your startup is for consumers and you don't have a

I'm pretty sure there's websocket (and related tech) support for your stack. I would explore this first. If your startup is for consumers and you don't have a good estimate of your growth or you don't know how fast your app will need to scale, then make sure you can hire people who know quickly. Your hiring skill will be more important than your tech. Also, if the complexity of your app is low or medium, consider your first implementation as a prototype that - given growth happens - can be replaced with a faster stack relatively simple. If high concurrency is needed, you'll bump into frameworks focusing on async I/O. Java and C++ implementations are the leader here. (see techempower benchmarks for more information). If you can commit to a datastore (and you rarely make a mistake by choosing PostgresQL), then replacing your prototype down the road is easier.