I think a PWA can do push notifications
Haven’t try that though.
derek-zhou
wmnnd
The nice thing about using LiveView (thanks to Elixir/Erlang underneath) is that it can scale very easily on a single machine. And it’s definitely possible to have several thousand concurrent connections on one machine with LiveView. So there might be no need to scale horizontally and increase complexity like that 
I would however recommend you do some actual load testing before deploying at scale 
4
Sebb
I think a PWA can do push notifications
Or you can use a push notification platform that brings its own generic app.
Still, there are reasons for the customer that makes an App mandatory. This seems to be the only reason for me not to go with LV. I don’t see why it should be a problem to have different roles of users. If anything LV is at the advantage here, the more complex the frontend is: the better not to write it in JS.
Obviously, if you have many concurrent users, the server has to keep up, but that is (relatively) easy with LV (and the tech behind it).
yes, good related reading for the topic. Phoenix Blog Post: Failing Big with Elixir and LiveView - A Post-Mortem
2
wanton7
I’m quite sure some companies have made hybrid mobile apps by using web view and just showing normal web site inside that app. Web site then communicates with the app to send notifications etc. Experience might not be as fluid as native app but I think it’s something to consider as well.
0
quatermain
It mostly depend on what HW you will use for production. We have project which run on single paid Web Dyno. We even didn’t notice that we had huge peak of users. It was like 600 000 per day and regular traffic was at that time less than 100. There are multiple LV collaboration forms and dashboards.
Yes, but it depends what you show on dashboard. What dashboard do? Just show information and it’s still same dashboard even when you have 10 000 connected users. Sorry, not when you show their names who is online on that dashboard ;). Let’s try think about regular flow. User open url → full page html is generated with a lot dashboard data → user see dashboard → user click on filters or next page in table → full page html is generated wit a lot of dashboard data
LV flow: User open url → full page html is generated with LV connection → LV send dashboard data → user click to filter → LV send only changed data in some table/whatever.
So from this point of view LV is even cheaper for traffic. If you have static dashboard without realtime data you don’t need LV for static page.
Ok, so you have LV with dashboard, state contain user struct, all entries, etc… everything works good. But 10 000 users are online. So 10 000x LV state. Yes, that can be issue, it can consume memory. So if you have machine with 8 GB memory I think you don’t have to care. If you have 512 MB Web server, that can be problem. It can be fixed with small refactoring and what Chris wrote temporary_assigns.
So I think we have to know more about what content you will show and store in state if you want to have proper answer for it.
I wrote article this topic last week. There is small discussion which can give you ideas which problem you can have in future with a lot of data https://quatermain32.medium.com/where-to-not-use-phoenix-liveview-7fb5ffb8318b
1
alaadahmed
You know that I wrote this topic here after I read your article!!
It is Linode Server (4GB Ram, 2 Dedicated CPUs, 80GB SSD)
Actually I use always temporary_assigns but sometimes it make unexpected behavior when I use it for listing with pagination
In brief: It is platform that will integrate zoom for live courses, google form form quiz and full calendar for student schedules. Also will use neo4j as database. Students will have their portal to manage their courses or subjects that they bought, check for incoming messages from their teacher or visors, send messages, check their notes board in case of any notes posted by teacher, download materials for their subject, check if there is assign homework for them, upload it, solve exams or quiz that assigned for them, make review about teacher, submit ticket for any complain or issues. This only Student portal, you can imagine also Teacher portal, Visor and Supervisor, Manager/Admin. There is a report mechanism or module that can be used by Supervisors or Manager to collect information about any Teacher / Student, there is evaluation for students and teacher. This is too much to write here but I think you get the idea
1
quatermain
oh, so maybe I was the evil on your shoulder, sorry 
So there are a lot of questions which have to be answered, for example:
- what content will you show?
- do you need api for mobile app?
- do you have budget(time,money,…) for custom FrontEnd work?
From my point of view if
- regular data about user, not dashboard with 1000 data set per user per dashboard
- no, maybe in far future
- no, no time, no budget
Go for LV
4 GB memory and 2 CPUs will be for app or for DB and web server too? It’s not enough for all of it even when you will use graphql and FE JS Framework when you will have 10 000 users.
1
alaadahmed
It is not for development, but deployment sure we can bump up the specs to as much as we need to
0
quatermain
I think you mean production. Ok so I think HW performance doesn’t have to be issue. You won’t be able to make messy code of course. Like load all entries, users, data, whole DB into LV state
0
quatermain
multiple LV app, about 100 users per day, sometime 1000s users but I don’t have data for these days.
3