One consequence of this design choice is that there are 9 separate Enums where currency is defined which is a maintenance nightmare

Question

One consequence of this design choice is that there are 9 separate Enums where currency is defined which is a maintenance nightmare

Opened this issue 3 years ago · 2 comments

Answer 1 · 2021-02-28T00:51:17.000Z

A good approach to that is the creation of business library packages shared across the different services. This way all the currency data would be present in the shared business package.

Answer 2 · 2021-03-27T21:57:26.000Z

There is indeed many code in this solution that adds a lot of complexity and duplicity along the different solutions and projects. As a solution to this problem Im going to shift the solution design to one solution project containing all the other projects and will apply Clean Architecture pattern across the whole stack.