I’m working on app which, at the moment, contains a few separate parts:
- A desktop chat app built with Electron.js (think Slack).
- A simple node.js server that the desktop app communicates with. The desktop app uses socket.io to send messages to this server, which in turn emits the message to all connected clients.
- A newly created Meteor.js app, which at the moment is acting as the download page for the desktop app, and a few other functions (like payments).
I have a few questions:
I’m thinking about scrapping the node.js app and implementing its socket.io functionality into the Meteor app. Some concerns include scalability. Will having a single Meteor.js app serve the web pages and receiving a bunch of socket.io messages cause scale issues? Is it better to keep my current architecture with a seperate node.js app for the chat system?
I need to implement user authentication in the Electron app so users can log in. If I decide to scrap the node.js app as mentioned above and just use the Meteor.js app, how can I connect Meteor’s default user system to the Electron app to allow users to login?