15. While .NET Core 3.0 was still in preview we tested Blazor
Server to see what its baseline scale characteristics look
like. We put a Blazor Server app under load with active
clients and monitored the latency of the user interactions.
In our tests, a single Standard_D1_v2 instance on Azure
(1 vCPU, 3.5 GB memory) could handle over 5,000
concurrent users without any degradation in latency.
A Standard_D3_V2 instance (4 vCPU, 14GB memory)
handled well over 20,000 concurrent clients.
https://devblogs.microsoft.com/aspnet/blazor-server-in-net-core-3-0-scenarios-and-performance/
16. ASP.NET Web Forms vs. Blazor
ASP.NET Web Forms Blazor
React/Vue/Angular のようなクライアント側 Web UI フ
レームワーク
UI 操作 ≠ HTTP リクエスト・レスポンス仕組み
サーバー側、ページベースアーキ
テクチャー
UI 操作 ⇒ HTTP リクエスト⇒ レ
スポンス
ページ自身へポストバック
or ASP.NET AJAX / UpdatePanel
コントロール
ページライフサイクル
ViewState でページ情報を維持
RenderTree → in-memory
representation of the DOM
31. https://www.telerik.com/blazor-ui
“Telerik UI for Blazor components have been built from the ground-up
to ensure you experience shorter development cycles, quick iterations
and cut time to market”
“DevExpress UI for Blazor ships with 12 UI components (including a
Data Grid, Pivot Grid, Charts and Scheduler) so you can design rich user
experiences for both Blazor server-side and Blazor client-side
platforms.”
https://www.devexpress.com/blazor
“The Syncfusion ASP.NET Core Blazor Components library is the only
suite that you will ever need to build an application, containing over 60
high-performance, lightweight, modular, and responsive UI controls in a
single package.”
https://www.syncfusion.com/blazor-components