I was asking around about how to structure a SaaS app I am currently developing an MVP for.In a very general overview, the Web SaaS App will be a Dashboard that will keep track of Orders (Can Add, Edit, Delete etc). My initial thoughts were that each Business that owns the SaaS will have an Admin account (access to sensitive info, credit card info etc.) and one general Employee Account (general access w/ shared username & password).With this line of thinking I asked:Question 1: Can all employees be logged in at the same time from different computers with the same username & password?(The general consensus seemed to be Yes. However, from an audit trail perspective (i.e. an employee can delete order and you wouldn't know who did it) it would be bad design.). Was advised to let each employee have their own username & password*Question 2: If, question 1 was true, will they be able to see an update instantly when Employee A makes an edit to an order and that information is saved to the backend database?(the general consensus seemed to be that this would best be achieved through WebSockets)My question is, do you agree with this consensus?If so, to my biggest question, is WebSockets in production extremely expensive and server-intensive?From my understanding, WebSockets keep a consistent connection between client and server. If I hypothetically have 10 business users with 5 employees each (with their own username & password), isn't that already 50 connections? Is this very costly to scale, especially with Heroku?
Submitted July 18, 2019 at 07:41PM by RSpringer242
No comments:
Post a Comment