MongoWebApiStarter VS Socket.io

I just started a project with a vertical slice architecture and got some inspiration from this https://github.com/dj-nitehawk/MongoWebApiStarter

this is the one we use for all our new projects.

yes that's what we do. op should just store the sensitive data as environment variables and let the .net config provider read those values during app runtime. you just need to use the double underscore format for naming the variable paths like so: https://github.com/dj-nitehawk/MongoWebApiStarter/blob/a86342d8585d6659dfd677b485f0f22813e9d861/Template/.linux-server-setup/env-variables.txt

if you feel like jumping heard first, have a look at this starter template i have on github. that's what our team uses for all new web api projects.

planning on doing a video tutorial series building a real world app. in the meantime have a look at this starter template project which handles some of that stuff: https://github.com/dj-nitehawk/MongoWebApiStarter

if you're familiar with mongodb, may i recommend an excellent web-api starter template by yours trully ;-)

if mongodb is an option, have a look at this starter template which uses vertical slice architecture.

here's a starter template project that i use.

look into servicestack and vertical slice architecture. check out this dotnet new template where I've implemented both: https://github.com/dj-nitehawk/MongoWebApiStarter

another huge fan of vertical slices here. but I do it without mediatr and use servicestack instead of mvc. here's an example: https://github.com/dj-nitehawk/MongoWebApiStarter

The first is the script tag in the head of our HTML document that loads the Socket.IO client library. This script tag includes the Socket.IO client library that will communicate with our socket.io server from the code above.

Before diving into this tutorial, if you find microservices mysterious, check out my previous article for a detailed explanation. In this hands-on tutorial, we'll build a real-time chat server using Node.js, Socket.io, RabbitMQ, and Docker. Get ready for a practical journey into the world of microservices! Let's begin.

Socket.io Docs

Now we will be implementing socket logic using socket.io for building websockets. This library provides an abstraction layer on top of WebSockets, simplifying the process of creating real-time applications. For better maintainability, it is recommended to create a separate file for socket calls. To do this, navigate to the src folder, create a folder named services, and inside it, create a file named socket.ts under the services folder.

Hi I made a chat app using socket.io it worked fine locally but when i deployed the app on render.com socket is not working properly i have to refresh the page to see new messages please help...

Nextjs + socket.io.. Planning to use webrtc for video calls later

Implementação em Node usando Socket.io

I am using socket.io for real-time notification service. Previously my frontend part was deployed in Netlify and here the notification was not working properly as Netlify follows serverless architecture.

yes. Im running on DreamCompute currently. Discord.js and socket.io within same app. A dedicated server works too, but pricier.

No, not a library. More like, the frontend and backend just happen to need the same version to be compatible (socket.io is a good example, moment.js was the most basic I could think of).