The 1st method - AMQP Message Publisher / Consumer
Overview
- This is the first way of communication:
- To publish events of application domain services using message broker
- To register subscriber and consume events of application domain services using message broker
- AMQP API is defined by AMQP protocol
- The event messages are supported by C# Contracts nuget package
- Native backend service can publish messages by AMQP exchanges
- Native backend service can consume messages by AMQP queues
See more: OIDC/OAuth2 authentication
Message Broker
MessageBroker is using AMQP protocol via 5601 port (TCP/SSL, outgoing) Message broker is protected by firewall and not accessible for external and on-premise integration solutions.
Important: Message broker is available only for native applications running on AVAplace platform, not for integrated external solutions.
Publish notification message using message broker
- How to publish AMQP message(s):
- Your AMQP API is defined by AMQP protocol
- Publish event(s) to publish AMQP message(s)
See examples:
Consume domain entity released event using message broker

- How to consume AMQP message(s):
- Register consumer(s) for event(s) to create AMQP message queue and to consume messages
- Use HTTP client to obtain payload when a message is delivered
See examples: