Web Development With Blazor: Introduction (Part 2)

By Ashwin Venugopal -

 





Blazor Server

Blazor Server uses SignalR to communicate between the client and the server, as shown in the following diagram:

Blazor Server or Blazor WebAssembly? Which one is better? Q3 2023 — Arad Haghi

SignalR is an open-source library for real-time communication that establishes a connection between clients and servers. It can utilize various methods of data transport and automatically identifies the most suitable protocol depending on the capabilities of both the server and the client. SignalR prioritizes the use of WebSockets, a transport protocol incorporated in HTML5. If for any reason WebSockets is unavailable, it will smoothly revert to an alternative protocol.

Blazor is constructed using reusable UI elements referred to as components. Every component comprises C# code, markup, and may also incorporate additional components. Razor syntax allows you to blend markup with C# code, or you can choose to write everything in C# if preferred. User actions (like clicking a button) or events (such as a timer) can cause the components to be refreshed.

The elements are organized into a render tree, which is a binary representation of the DOM that includes object states along with their properties or values. The render tree monitors any alterations from the last render tree and transmits only the modified elements over SignalR using a binary format to refresh the DOM.

On the client side, JavaScript will capture the modifications and refresh the page as needed. Compared to conventional ASP.NET, we solely render the specific component rather than the whole page, and we transmit only the actual changes to the DOM instead of the complete page.

Disadvantages Of Blazor Server

  • You must maintain a constant connection to the server because the rendering occurs on the server side. If your internet connection is poor, the site may fail to function properly. The main distinction from a non-Blazor Server site is that a non-Blazor Server site can send a page and then drop the connection until a new page is requested. In contrast, a Blazor site requires that connection (via SignalR) to remain active at all times (short disconnections are acceptable).

  • There is no offline/PWA mode since it needs to be connected.

  • Every interaction or refresh of the page necessitates a return trip to the server, potentially leading to increased latency. It's essential to note that Blazor Server transmits only the updated data.

  • Given the need for a connection to the server, the demand on that server rises, making it challenging to scale. To address this issue, you can utilize the Azure SignalR hub, which will manage the continuous connections and allow your server to focus on providing content.

  • To be able to run it, you have to host it on an ASP.NET Core-enabled server.

Advantages Of Blazor Server

  • It includes the necessary code to confirm that the connection is transferred to the client, allowing the site to maintain a minimal footprint.

  • As we are operating on the server, the application can fully utilize the server's resources.

  • The site will work on older web browsers that don't support WebAssembly.

  • The code operates on the server and remains there, it cannot be decompiled.

  • Given that the code runs on your own server (or in the cloud), you can directly access services and databases within your organization.

Conclusion

Details about Blazor server and its advantages as well as disadvantages are discussed. 

















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