4 ms·
> Use a framework that understands your schema / data storage system. The whole supposed premise of golang is that it shuns frameworks. What frameworks do you
by gher-shyu3i 5y ago
> Use a framework that understands your schema / data storage system.
The whole supposed premise of golang is that it shuns frameworks. What frameworks do you recommend in golang for such applications?
You're still going to end up writing mapping logic back and forth between your RPC layer, internal layer, and DTOs. It's extremely verbose and error prone in golang to manually write them.
- kardianos 5y agoI'm not suggesting you use a web-framework. If you write a business application, first have an application framework, specific to your application. And no, you won't have mapping logic between RPC and internal and DTO. Most people don't understand how to build an application. They think in terms of RPC and encoding, not in terms of Screens, Actions, and Workflows.
- gher-shyu3i 5y ago> first have an application framework, specific to your application. So we're reinventing the wheel each time no? > And no, you won't have mapping logic between RPC and internal and DTO. How would it work then? Use the same DTO across the board?
- sagichmal 5y ago> Most people don't understand how to build an application. They think in terms of RPC and encoding, not in terms of Screens, Actions, and Workflows. What are Screens, Actions, and Workflows?