Home/ Questions/Q 7816151
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-06-02T05:45:48+00:00

My CQRS-based architecture currently has 4 components. It is more of a prototype so

  • 0

My CQRS-based architecture currently has 4 components. It is more of a prototype so nothing is set in stone yet.

  • CommandProcessor: Gets commands, executes them, etc. (duh ^^),
    publishes events. Is Azure-based
  • ViewProcessor: Gets view-requests,
    responds with the view. Subscribes to events to update view store. Is
    Azure-based
  • WebClient: AJAX-heavy web portal, sends commands and
    requests (json-)views. Azure-based
  • DesktopClient: Not much to say,
    also sends commands and requests views (undecided if json or some
    other format). Obviously not azure-based.

My original approach was to use an InMemory-Viewstore. Azure VMs have quite a bit of memory available and I didn’t really see the need to add the complexity Blob-Storage etc.
Additionally, I am trying to minimize the command-execution latency to at least partially get around the whole asynchronous UI problem so that I can (where needed) simulate a synchronous UI with (fast) callbacks (I hope that sentence made sense ^^).

In creating the web client, I noticed a potential flaw in my plan. The url of the ViewProcessor is obviously different to the WebClient-url, so json requests would fail because of the Same-Origin-Policy. Alternatives/Workarounds like jsonp did not seem that attractive because they don’t solve the inherent security problem. Implementing the ajax requests to target the WebClient itself would be an option but then I would have redundant functionality (view-store in both webclient and viewprocessor).

I guess saving the views in blob-storage would solve this problem, but I can’t shake the feeling that I am overlooking something important/obvious. 

    Client --command-- CommandProcessor
    CommandProcessor --event-- ViewProcessor
    ViewProcessor --view-- Blob
    (ViewProcessor or CommandProcessor) --notification-- Client
    Blob --view-- Client

That scenario would have quite a bit of latency 😐

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    I would look again the blob storage option. We store serialized view objects in blob storage, and it is very fast and stable. Is there some aspect of blob storage that concerns you?

    Erick

    • 0