How quyvu01/anemoi_open works
Main Components
• Anemoi.BuildingBlocks – the shared libraries, core utilities, and foundational components.
• Anemoi.Centralize – the API aggregation layer that clients interact with (acting as an API gateway).
• Anemoi.Contract – a shared DTOs and contracts library that standardizes data transfer.
• Anemoi.Grpc – the gRPC-based communication component for high-performance inter-service calls.
• Anemoi.Identity – microservice handling authentication, authorization, and identity management.
• Anemoi.MasterData – service for serving static or reference/master data.
• Anemoi.Workspace – service for managing user/resource-specific configurations.
• Shared Infrastructure & Communication:
• A message broker (RabbitMQ) should be shown as the backbone for the event-driven design.
• Optionally, illustrate database components wherever Entity Framework is used (each service likely has its own persistence model).
Important Architectural Patterns and Design Elements
• For Saga orchestration, you might want to show a control component or coordination mechanism that manages distributed transactions across microservices. Annotate it as “Saga Orchestrator” if it is implemented as a part of one of the microservices (or an external coordinator).
Technologies, Frameworks, and Integration Points
• GRPC as the protocol for high-performance internal communications (linking Anemoi.Grpc with other services).