Describe the solution you'd like
We need to copy the current transactions executor service into a standalone microservice dedicated to executing transactions, while possibly keeping the original package as an integrated AIO solution. The new service should be responsible for processing transaction requests, handling their status, and communicating with the rest of the system in a decoupled, scalable way, in the same way however that it is already implemented in the transactions package. This will help us achieve better modularity, scalability, and maintainability, enabling independent scaling and development of transaction-related features.
The Transactions Microservice will:
Handle transaction creation, processing, validation, and status updates (e.g., pending, completed, failed).
Expose RESTful APIs for interacting with the main application and other services.
Use event queues to notify/be-notified other services of transaction events (e.g., completed or failed transactions).
Include features in future releases like logging, auditing, and retry mechanisms to ensure transaction integrity and reliability.
Describe the solution you'd like
We need to copy the current transactions executor service into a standalone microservice dedicated to executing transactions, while possibly keeping the original package as an integrated AIO solution. The new service should be responsible for processing transaction requests, handling their status, and communicating with the rest of the system in a decoupled, scalable way, in the same way however that it is already implemented in the transactions package. This will help us achieve better modularity, scalability, and maintainability, enabling independent scaling and development of transaction-related features.
The Transactions Microservice will:
Handle transaction creation, processing, validation, and status updates (e.g., pending, completed, failed).
Expose RESTful APIs for interacting with the main application and other services.
Use event queues to notify/be-notified other services of transaction events (e.g., completed or failed transactions).
Include features in future releases like logging, auditing, and retry mechanisms to ensure transaction integrity and reliability.