MIDAZ reorganization structures

[MartinezAvellan]

Context

We will implement structural changes in Midaz with the goal of improving transaction performance, enabling the application to achieve higher TPS (Transactions per Second).

We currently work with two applications in Midaz, isolating domains and data access. This isolation has caused performance issues during transactions, as any communication related to accounts involves the transactions application communicating through gRPC requests.

How to do it?

Given the context above, we have decided to simplify the application and remove the gRPC connection, allowing the applications to communicate directly with the database and reduce processes during a transaction.

We have also decided to rename the app ledger to onboarding, as the application’s focus will be on managing CRUD operations within the Onboarding and Portfolio domains, while the transaction application will directly handle account balances.

Below is a brief overview of the change:

Now:

New:

[tonicospinelli]

Could you share what kind of reorganization is needed?
I'm thinking of contributing to the project in my free time

[MartinezAvellan]

I’m glad! Soon after this transition, we will resume with more tickets.

This restructuring has two types:
• an implementation to align with business rules,
• removal of code to improve the performance of the transactional layer.

This ticket is already being worked on with these changes.

[fredcamaral]

Making it a bit more detailed for archive: this is a structural change that is needed to improve transactions' TPS. We are currently storing balance in a domain different from the transaction domain. This requires a gRPC comms between two different domains that could be better fine-tuned (the POST transaction). The idea is to make the transaction to be authorized within the same domain context to avoid the gRPC just to check the balance.

[gitfelipegomes]

@tonicospinelli I’ve added the context of the changes to provide greater visibility. Feel free to reach out with any additional questions if needed.

[fredcamaral]

(syncing github issues with jira)

[gitfelipegomes]

We decided not to proceed with the change mentioned above. Instead, we will implement a token cache solution in Auth to avoid low performance in call authorization, which was impacting transaction performance.