Trading Partner Service
Component basics
Title | Trading Partner Service |
Description | The trading partner service contains the configuration of trading partners from whom the EDI files are received for processing the HIX Enrollments. The trading partners hosted in this service can be created or updated from the Zeus User Interface. The trading partner service contains several APIs that other microservices use to determine the trading partner to be associated with the transaction. The trading partner association will link the state, marketplace type, line of business to the transaction. |
Anatomy diagram |
|
Key to anatomy diagram |
Specifications
Microservice Tech Stack | The microservice is build in Java 17.0, with Spring 6.0 Framework and Spring Boot 3.0 |
|---|---|
Database | For local the MySQL database is used. For Docker the MariaDB is configured to be used. For Unit Testing, H2 database is used. |
Messaging Service | Kafka is used for asynchronous communication between Account Processor and other services |
Style |
Additional guidance
Content | |
|---|---|
Accessibility | |
Mobile | |
Best practices | |
Related |