Parse-Server VS Socket.io

Parse-Server Reviews

Socket.io Reviews

Parse-Server mentions (5)

• What to choose for backend

  If you like headless CMS / Backend As A Service you should consider https://directus.io/ or https://github.com/parse-community/parse-server. Both nodejs and open source. Source: almost 2 years ago

• Any general purpose visualisation "just add the data" framework

  There's numerous standard backends which frontenders could use in simplistic cases to start, say https://github.com/PostgREST/postgrest or https://github.com/parse-community/parse-server. Source: over 2 years ago

• Show HN: Caffeine, minimum viable back end for prototyping

  Parse is still around and supported: https://github.com/parse-community/parse-server. - Source: Hacker News / over 2 years ago

• Ask HN: What Back End Framework with User Management Is Your Favorite?

  I am curious what backend framework you would choose to run with for prototyping an application with run of the mill user management requirements. That is functionality along the lines of: session management, password policies, password reset, user verifications, etc. Sadly it seems there really aren't any frameworks that have user management natively supported. The only one I am aware of is [Parse... - Source: Hacker News / almost 3 years ago

• [Open Source] I made my first app. Its a fully functional social media app. And I decided to open source it.

  I believe you are referring to main.js file. The answer is no. I used parse server for backend. And by default all classes are public which means everyone can read every data. There is a preferred way to prevent this. You disable all class level permissions for every class. Then you put your app logic to cloud code which is main.js file you were looking at. Here is an article about this... Source: about 3 years ago

Socket.io mentions (716)

• Mastering Microservices: A Hands-On Tutorial with Node.js, RabbitMQ, Nginx, and Docker

  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. - Source: dev.to / 3 months ago

• WebSockets Unlocked: Mastering the Art of Real-Time Communication

  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... - Source: dev.to / 3 months ago

• Socket io not working on deployed version

  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... Source: 5 months ago

• Hi guys, just wanted to share that I tried to create a better omegle alternative. Open to any feedback!

  Nextjs + socket.io.. Planning to use webrtc for video calls later. Source: 5 months ago

• Does the MERN app with socket.io work correctly in the Google app engine?

  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. Source: 5 months ago