I agree that it is not a scalable architecture but unfortunately it is a large
third party application the business depends on and it cannot be rewritten.
Option 3 to use grpc is a good idea but unfortunately won’t work either because
the Go shared library invokes C function calls back into the
That does not sound like a scalable architecture!
The number of simultaneous user connections the architecture can support is
limited to the number of processes
your server can run. The resources required by a process are orders of
magnitude more than those required for a goroutine.
And the Go
The multiple instances are required to due to way the 3rd party application
works. In brief, it creates a new process for each user connection and then
each new process dynamically load the Go shared library to provide C extension
points.
--
You received this message because you are subscribed
> However, due to the nature of the application, there maybe 100 or 200
instances
Interesting...
Could you elaborate the nature of the application, and why a single
instance is not enough...
--
You received this message because you are subscribed to the Google Groups
"golang-nuts" group.
To
