title: Blazor WebAssembly - use SignalR or Controller actions for basic operations?
body: <p>I normally develop with ASP.NET MVC, but I'm very new to Blazor. I'm creating a new site in Blazor WebAssembly. The very first thing I need to do is create a page with a simple form, that can create or update an item and send it to the server, to be saved in the DB. I can either send the object using SignalR, or use HttpClient to post it to a controller action. What's the best practice here in Blazor Wasm? I was tempted at first to just use SignalR all the time.</p>
  <p>I've seen examples of using both, but very little to help decide which to use in what circumstances. <a href="https://softwareengineering.stackexchange.com/questions/262045/is-performance-the-only-reason-not-to-use-signalr-websockets-entirely-in-lieu">This</a> was about the most useful thing I could find but it doesn't answer the exact question and it's also not specific to Blazor.</p>
  <p>The question is specifically about the simple create update operation, but other pros and cons of both would be very helpful. Is it as simple as &quot;only use SignalR when clients need to listen for messages from the server, to avoid having too many open connections&quot;?</p>
  <p>Thanks a lot</p>