The 1st method - 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 or message gateway
• Native backend service can publish messages by AMQP exchanges
• Native backend service can consume messages by AMQP queues
• External cloud service can consume messages by gRPC (.NET only) or Webhook channel
• External on-premise service can consume messages by gRPC channel (.NET only)

See more: OIDC/OAuth2 authentication

Message Broker

MessageBroker uses the AMQP protocol on port 5601 (TCP/SSL, outgoing). Message broker is protected by firewall and not accessible for external and on-premise integration solutions.

• Consume messages using message broker using AMQP - for native applications only
• Publish messages using message broker using AMQP - for native applications only

Message Gateway

MessageGateway is microservice encapsulating external communication with message broker to HTTP based technologies, gRPC and Webhooks. It is the preferred way for external cloud and on-premise services integrated with AVAplace platform.

MessageGateway API base URL: https://{hostname}/api/asol/msggw

• Consume messages using message gateway using gRPC
• Consume messages using message gateway using Webhook