title: Blazor WebAssembly (Hosted) MicroService Strategy
body: <p>The guts of my application is made up of a suite of microservices, with each mostly using DDD Architecture.</p>
  <p>In a standard MVC solution, the client would access my controllers and the controllers would interact with my microservices.</p>
  <p>In a Blazor Server setup, the approach would be similar.</p>
  <p>However, with a Blazor WebAssembly (Hosted) setup I have the opportunity to reference my microservices directly from the Blazor WebAssembly Client.</p>
  <p>Is this wise?</p>
  <p>Or would I be better off creating a facade on the Blazor server (which in turn accesses the microservices) and only communicate with that facade from the Blazor WebAssembly client?</p>
  <p>My Blazor Server has its own needs to reference the microservices and I was just about to register the microservices on the client as well before wondering if this was sensible.</p>