AC 5.x Application Architecture

webapp-gateway

• Microservice to serve as a single entry point for communicating with all the Microservices

• Invokes multiple Microservices and aggregates the results.

portal

• Microservice for serving GUI to configure entities and view logs.

web-runner

• Microservice for serving UI data.

event

• Microservice for scheduling of events

runtime

• Microservice for Process Flow and Transaction execution

rest-api

• Microservice to publish and serve all the REST API

soap-api

• Microservice to publish and serve all the SOAP API

listener

• Microservice for the execution of listeners (Only one instance/Pod will run at a time).
  The following listeners are part of this microservice. For more details on how to work with these listeners, refer to their respective pages.

1. JMS

   • Spazio MFT

   • MLLP

   • SAP

   • Kafka

ai-mapper

• Microservice for AI-based auto mapping.

license

• Microservice to register and enforce licensing.

api-gateway

• Microservice to serve as a single entry point for all the REST and SOAP API calls.

archival-and-cleanup

• Microservice for log cleanup and archival.

rabbitmq

• For facilitating asynchronous inter-service communication.

• Back pressure handling: queueing jobs, routing to dedicated pods, Autoscaling based on queue size.

PV/PVC

• Repository for persistent storage of runtime temporary files and for archiving.

Database

• Backend Database – Stores all metadata related to users, transactions, configurations, and partners.

• Log Database – Stores all run time execution details, log information, and audit trails.