I don't recommend that you use Vue but that is just my biased opinion for react against vue. If you want a better user experience, use Next.js server side rendering. You will need to use Web Assembly to compile your unity 3d game on the web. DO NOT use html, css and js for your game. I recommend you use a tailwind UI kit, Chakra UI or material UI.
I would recommend that you create a firestore collection for all the blogs that you use. You do not need Graph QL, wordpress or Strapi because you are using next.js. Just use ISR(incremental static regeneration) to make a blog.
Hey!
Strapi works with Next.js like a charm, it's fast, customizable, and the new version 4 is very powerful. You may find a couple of tutorials here https://strapi.io/integrations/nextjs-cms, and there are many video tutorials on Youtube. The Strapi website is actually build with Strapi and Next.js https://strapi.io/blog/how-the-strapi-marketing-team-uses-strapi
My web app will use redisJSON and/or MongoDB. I need my app to have real-time functions. I don't want to run my Next.js app with a dev server on the node. I want to use vercel's hosting with static side generation only. Do I use pusher or Socket.IO? Or maybe some tool I don't know about.
Key thing to understand here is that you are hosting data & logic somewhere. Socket.IO requires you to host and manage a dev server somewhere (as the previous suggestion mentioned Heroku is a good choice)
However, It's not really in keeping with the serverless world that Vercel provides and its a headache to scale and manage. We (I work at Ably) have a bunch of open source examples of how all this works. Ably provides serverless N to N connectivity, along with first class integrations into serverless functions on AWS, Azure, cloudflare and GCP. This allows you to build a realtime, serverless system that you can scale without any pre provisioning.
Nothing is totally free but you can get away with the free tiers on all of these services for a lot longer than you may think.
It really depends on how you want to do it. If you use Socket.IO, you do have to have your own server running somewhere else, a good free one is Heroku. Pusher is nice if you know what you are trying to do, know your limits, and how to do it. While Socket.IO allows more flexibility if you need to do something crazy, Pusher is great if you're just doing standard real-time data transfer because there is minimal setup. The only other thing about Pusher is that it is not entirely free, so if you know the pricing, know how much you are going to use, and are willing, you could easily use Pusher.
