Where are you thinking this operating cost is coming from?
There are types of applications that can not presently be built with DWAs, but that doesn’t mean that will be the case for much longer. It’s not due to a technical impossibility, rather a lack of existing libraries to make it easily done. No one has built it yet, that’s all. I’ll get there if someone else doesn’t beat me to it.
Here is a diagram of how asynchronous messaging can work:
It will scale horizontally as high as the host browser will allow (in WebRTC connections), taking into account the host machine. If the connections are not persistent, and are rolling/transient, then one instance could probably serve thousands of users simultaneously.
You can use this topology to do a lot. You’re not limited to just messaging, a Discord clone or anything group-oriented would be very simple this way, for example.
Where are you thinking this operating cost is coming from?
There are types of applications that can not presently be built with DWAs, but that doesn’t mean that will be the case for much longer. It’s not due to a technical impossibility, rather a lack of existing libraries to make it easily done. No one has built it yet, that’s all. I’ll get there if someone else doesn’t beat me to it.
Here is a diagram of how asynchronous messaging can work:
It will scale horizontally as high as the host browser will allow (in WebRTC connections), taking into account the host machine. If the connections are not persistent, and are rolling/transient, then one instance could probably serve thousands of users simultaneously.
You can use this topology to do a lot. You’re not limited to just messaging, a Discord clone or anything group-oriented would be very simple this way, for example.