It's a bit more complicated than that. WebSocket and Server-Sent events cannot be really used interchangeably. Each addresses a different situation. If your backend architecture is event-driven, you'll have to use WebSocket (or MQTT or long/short polling). It's because in an event driven arch, a request to the backend will normally trigger a chain of asynchronous calls to multiple microservices. Once an incoming request leaves the boundary of the first microservice it will be forgotten and left to the broker, and server-sent event solution is almost impractical in this situation (the first microservice that handles the HTTP request should wait…
CQRS stands for Command Query Responsibility Segregation. It promotes the idea of separating the “responsibilities” of “commands” and “queries”. In this article, I will try to answer the following questions:
Let’s start with a classic example: an online ordering system for retail items. The application has two main use cases:
I am a technical architect and consultant, primarily working in the financial services industry.