Hi All, Forgive me if I posted in the wrong group, as it could be more of a question related to design patterns rather than to golang itself.
*The context* Imagine to create a full portal with users, profiles, ... and multiple services that can be activated for different customers. I can organise the code of my portal in modules so to have a "quite" clear use of golang packages, but at the end of the day I get to a unique EXE file that represents my server/portal. When I start it, the portal runs. Perfect. To make an example, think of google, where you have Drive (Service 1) and Gmail (Service 2). *MY DOUBT* If I want to fix a bug (or add a feature to) in Service 1 without affecting the use of Service 2 how do I do? Having a unique exe file, from my understanding I see that I need to fix the bug, build a new exe and deploy that one. In other words I can't but to restart the full portal just to touch one part of it. In Layman terms, if I had a portal in php I could (of course it depends on situations) simply replace the pages of the module for the Service 1 without the need to stop everything (not only Service 2,3,4 and so on but the whole portal). 1. Is there a simple design pattern to face a similar scenario? 2. Should the portal be made of more exe files, one for the main portal, one for each Service/Product? it worries me in terms of complexity of the organisation of coding... and I do not know how I would pass stuff between the main exe (listening and serving http calls) and the modules that woud take care of services... I hope my explanation makes sense. Well, honestly I hope it is a silly question as it would mean that the solution would be simple as well.. :) Thanks -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
