Web Development With Blazor: Introduction (Part 3)

By Ashwin Venugopal -

 






Blazor WebAssembly

Rather than operating Blazor on a server, you can also execute it within your web browser through WebAssembly. The WebAssembly variant of Blazor functions in a manner quite similar to the server version.

A render tree is still generated, and rather than executing the Razor pages on the server, they are now executed within our web browser. Because WebAssembly lacks direct access to the DOM, Blazor updates the DOM through direct JavaScript interoperation instead of using SignalR.

Disadvantages Of Blazor WebAssembly

  • When compared to other major websites, the size of a Blazor WebAssembly is substantial, and it requires downloading many files.

  • In order to utilize any on-site resources, it is necessary to create a Web API for access. Direct access to the database is not permitted.

  • The code operates within the browser, indicating that it is susceptible to decompilation. This is a situation that all application developers are familiar with, but it may not be as typical for web developers.

Advantages Of Blazor WebAssembly

  • Given that the code operates within the browser, developing a Progressive Web App (PWA) becomes straightforward.

  • As there are no applications running on the server, we can utilize any type of backend server or even a file sharing option (there's no requirement for a .NET-compatible server in the backend).

  • The absence of round trips allows for quicker screen updates (which is why some game engines utilize WebAssembly).

Blazor WebAssembly versus Blazor Server

It depends on which option we should select. If you have an existing site that you want to migrate to Blazor, opt for server-side. After you've completed the migration, you can then decide whether you want to pursue WebAssembly as well.

If your website operates on a mobile browser or an unreliable internet connection, you may want to explore an offline-capable option using Blazor WebAssembly, as Blazor Server requires a continuous connection. Although the initial load time for WebAssembly can be somewhat sluggish, there are methods to integrate both hosting models so you can enjoy the advantages of each.

Conclusion

A summary of the various technologies compatible with Blazor is presented. This can assist individuals in making a well-informed choice regarding which technology to select for their upcoming project.

 

 

 












Comments

Post a Comment

Popular posts from this blog

Deployment (Part 3)

By Ashwin Venugopal -
Image
  To read part 1, please click  here To read part 2, please click  here Microsoft Monitoring Agent (MMA) MMA is used across multiple Microsoft solutions and has undergone a few name changes as its features and functionality have evolved. If it is being considered to be used, then following areas should be covered during a Microsoft Sentinel deployment project: Consider the timelines and the strategy for a migration to AMA (Azure Monitor Agent) before the MMA end-of-life.  Consider the central deployment and management methodology for MMA. Determine which endpoints are in scope for deployment as these affect the log ingestion volume significantly.  Azure Monitor Agent (AMA) Organizations with MMA as the main Microsoft Sentinel agent should start planning the migration to AMA as soon as possible to avoid a rushed migration. One of the main advantages of AMA is the ability to control the log collection policy centrally and apply different policies against different...
Read more

Deployment (Part 1)

By Ashwin Venugopal -
Image
  To read part 2, please click  here To read part 3, please click  here Azure Resources Microsoft Sentinel needs following resources to be created: Subscription (if a dedicated subscription(s) will be used) Resource group(s) Log Analytics workspace(s) Automation rules/playbook Alert rules Workbooks Microsoft Sentinel offers hundreds of alert rules, workbooks, and automation playbook templates along with hunting scripts. The templates can be used to activate/deploy schedule alerts, create customized dashboards, create automation playbooks and perform threat-hunting activities. Generally, once deployed, the resources created have to be adjusted to match the existing environment, configure local credentials, etc. Methods of deployment: Manual- Administrator can manually configures the Microsoft Sentinel resources with the help of Azure portal. Any manual process has the inherent risks of human operator error, lack of compliance with potential change control procedures, and u...
Read more

Deployment (Part 2)

By Ashwin Venugopal -
Image
  To read part 1, please click  here To read part 3, please click  here Microsoft Sentinel Content Hub Content in Microsoft Sentinel includes any of the following types: Data connectors offer log ingestion from different sources into Microsoft Sentinel. Parsers give log formatting/transformation into ASIM formats, supporting usage across various Microsoft Sentinel content types and scenarios. Workbooks provide monitoring, visualization, and interactively with data in Microsoft Sentinel, highlighting meaningful insights for users.  Analytics rules give alerts that point to relevant SOC actions via incidents.  Hunting Queries are used by SOC teams to proactively hunt for threats in Microsoft Sentinel. Notebooks help SOC teams in using advanced hunting features in Jupyter and Azure Notebooks. Watchlists support the ingestion of specific data for enhanced threat detection and reduced alert fatigue.  Playbooks and Azure Logic Apps Custom Connectors provide featu...
Read more