2 ms·
How do you suggest getting rid of DAO/DTO? This has nothing to do with Java, but with the domain at hand. I worked on several golang projects where protobuf wa
by seer-zig 4y ago
How do you suggest getting rid of DAO/DTO? This has nothing to do with Java, but with the domain at hand.
I worked on several golang projects where protobuf was used, and the same dichotomy showed up in the code. There were three types even, protobuf types, internal types, and DB types, with manual mappers and validators having to be written between them. Quite a bad, verbose, and error prone experience, especially that golang itself is quite verbose.
- sandGorgon 4y agohere's my thought - and ill be the first to admit that i may not be correct. its the front loading of a huge number of patterns which ends up being the barrier. An argument is made for "future proofing". Its not unlike Python whitespace indentation or golang's unused variables restriction. But the design pattern complexity is far more harder than all these things. There is a certain degree of complexity when all of this starts making sense. Or maybe do what Redux did ... and abstract everything out to somewhere else.