Application architecture

Owned by Nitin Beri (Unlicensed)
Last updated: Dec 08, 2021 by Ashhad AlamVersion comment
2 min read

Adeptia Connect (AC) is an enterprise-class application that is designed for reliable, scalable, and secure operations in mission-critical use cases. Large organizations such as many Fortune 500 companies rely on Adeptia Connect to handle important data exchanges with external customers and partners as well as within internal systems and applications.

Adeptia Connect version 4.0 is a cloud-native application with microservice architecture. It uses Docker to containerize different microservices and uses Kubernetes for container orchestration and management. The application provides the following advantages:

  1. It can run as a cloud-native application.
  2. High scalability. Different microservices can be scaled as per need.
  3. High availability.
  4. Automated deployment and upgrade through CD pipeline.
  5. Centralized monitoring and logging.

The Application Architecture diagram for Adeptia Connect is shown below.

Key components

ComponentDescription
API Gateway
  • Microservice for providing custom API to each client to connect with the requested Microservice.
  • 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.

Events

  • Microservice for scheduling of events

Runtime

  • Microservice for Process Flow execution

Webservices

  • Microservice for web service provider execution.

RabbitMQ

  • For facilitating asynchronous inter-service communication.

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

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

    1. JMS (Topic)

    2. Spazio MFT

    3. MLLP
    4. SAP
AI Map
  • Microservice for AI based auto mapping.
PV/PVC
  • Repository for persistent storage of run-time temporary files and archiving.
Database
  • Backend Database – Stores all metadata related to users, transactions, configurations, partners.
  • Log Database – Stores all run time execution details, log information, and audit trails.

External and inter-service communication 

External and internal communication in Adeptia Connect happens in the following manner.

  • Synchronous external communication happens using REST protocol over https.
  • Synchronous inter-service communication happens using REST protocol over https.
  • Asynchronous inter-service communication happens using RabbitMQ Message broker.

Technology Stack

Technology Stack section is still in progress and it's going to have content as we proceed to the GA release of the application.
You may be interested in...
What's new
Key terms
Install
Usage scenarios