The latest articles on DEV Community by Abhishek Shah (@abhishek_shah_379a7711fa9). https://dev.to/abhishek_shah_379a7711fa9 https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F3683556%2F6e291bd8-9ee8-4a8b-a879-77854ab0921f.jpg https://dev.to/abhishek_shah_379a7711fa9 en Abhishek Shah Wed, 24 Jun 2026 04:10:33 +0000 https://dev.to/abhishek_shah_379a7711fa9/how-do-you-do--d59 https://dev.to/abhishek_shah_379a7711fa9/how-do-you-do--d59 <p>From another programming language and recently picking in GO. I'm trying to understand how do you do things let suppose i have many services and storage,handler one things i often hear is that dependencies should flow in one direction and that components should depend on interfaces rather than concrete implementations. My confusion is about wiring everything together . If i have many services,handlers storage, then should i have to dump every things in main like initiating each storage in main then passing db pool , initiating each services then passing that storage to each of them as fallows handlers. Does this is the way i have to do or what ? doesn't it will make main function large , do you do the same for production code too. I'm also curious about what architectures people actually use in production go codebase</p> <p>thanks! </p> architecture beginners discuss go