简体   繁体   English

Blazor 服务器端和 WebAssembly 有什么区别? 两者的主要优点

[英]What is the Difference Between Blazor Server-Side And WebAssembly? And Main Advantages of Both

Blazor Provides us 2 ways of Hostings Models: Blazor为我们提供了两种托管模式:

  • Server Side服务器端
  • Web Assembly Web总成

Out of Hosting Differences.出于托管差异。 Are they any Differences Between those (in performance for example) and when should we use one over the other?它们之间是否有任何差异(例如在性能方面)以及我们何时应该使用其中一个?

I use the Following link As a Guide but I would like to hear different opinions in terms of practice about people who have implemented it我使用以下链接作为指南,但我想听到关于实施它的人在实践方面的不同意见

The main (and only) advantage of Blazor Server side is a much shorter development cycle. Blazor 服务器端的主要(也是唯一)优势是开发周期短得多。 Your UI code can directly call into repositories and server-side business logic.您的 UI 代码可以直接调用存储库和服务器端业务逻辑。

When you develop a WebAssemlbly app you will need an extra API layer for everything that has to happen on the Server.当您开发 WebAssemlbly 应用程序时,您将需要一个额外的 API 层来处理必须在服务器上发生的所有事情。

Blazor server also makes your Server a CPU and memory bottleneck because it has to maintain all the client's state. Blazor 服务器还使您的服务器成为 CPU 和 memory 瓶颈,因为它必须维护所有客户端的 state。

声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.

 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM