If your talking about creating a Golang Application Server, where multiple unrelated goroutines are running together, and loaded seperately as well. This is possible, I suppose, using the new v1.8 plugin architecture. You could have the managing central main goroutine load the plugins on demand, and kick off the code.
But you'll be missing a lot of standard and vital components from other application servers. There will be no real sandboxing. All the plugins will be sharing the same memory with no control stopping one from accessing the memory and resources of another. Furthermore you wont' be able to unload or reload an "application" (plugin). Frankly you're better off just running the applications as separate processes. You can always whip up an external managing process that starts and restarts them, just like init.d of runit On Monday, November 28, 2016 at 9:47:19 PM UTC-8, Thaniyarasu Kannusamy wrote: > > we all knows that sharing "Linux Kernel" is possible in container world. > i also want to know further that, > is sharing "Go Runtime VM" is possible in anyway ? > so we can able to share a common "Go Runtime VM" for many go application. > if that is possible then we can able to run 'Go Runtime VM' effectively in > serverless architecture. > > i know that 'Go Runtime VM' must be start from a "func main()" > > Thanks > Thani > -- 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.
