3 ms·
Just checked our newest Blazor server-side web administration site in chrome devtools. 12 requests total, 322kB transferred (914kB uncompressed, so either way)
by bob1029 6y ago
Just checked our newest Blazor server-side web administration site in chrome devtools.
12 requests total, 322kB transferred (914kB uncompressed, so either way), finish in 991ms. Request was made between Texas and AWS us-east-1. Server running on a T3a instance. This is .NET Core 3.1 on Windows Server 2019.
Of the 322kB, blazor.server.js is 39.2k and our JS interop shim is 3k. This represents all that is required to communicate between server and client. The rest of the static source is ace code editor, bootstrap, jQuery and open iconic. All remaining interactions happen as deltas over the websocket connection.
Every day that I work with Blazor, I am further convinced that it is the only way to build our web applications moving forward. I don't have a good answer for Blazor server side in mass-scale public-facing scenarios (a la Netflix), but anyone can come up with an edge case to poke holes. Our 'internal' dashboards are actually accessible from the public web and we have not experienced any DDoS or other performance incidents. If something does come up, I will just pop the VM over to the internal network & require VPN access. That said, I really prefer accessing Blazor server side apps as directly as possible due to the latency concern.
- ksec 6y ago> Blazor Does that mean LiveView? I guess we need a term for that since every framework is using a different name for it.
- tester756 6y agoThat's pretty interesting So, instead of sending tons of js on the client side that does the job, let's connect via websocket to the server and let the server return HTML with new content dynamically, yea?
- bob1029 6y agoCorrect. The way Blazor produces DOM updates is pretty interesting. There was an excellent NDC talk that does a deep dive on how all of the internals work: https://www.youtube.com/watch?v=dCgqTDki-VM https://www.youtube.com/watch?v=dCgqTDki-VM The amount of javascript interop that I have to maintain in order to support a very complex Blazor application is somewhere around 200 lines at the moment.