You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently we have 2 options how moskito instances could be registered in servers list in standalone moskito inspect application:
configuration (remotes in moskito-inspect.json)
quick connect from ui
Maybe we have more options, but i didn't made deep research.
And for big and dynamic production environments where everything is deployed frequently with containers with automatic scaling (based on load) this is not working approach (i'm about static configuration in moskito-inspect.json).
And we need some SPI for moskito (client role) when each application where moskito-core+rmi_api is integrated can register self in our "private registry" through own implementation.
And also we need some SPI for moskito (server role) (in our setup this is standalone moskito-inspect war application) through what we can resolve (from our "private registry") all running moskito instances.
For different projects/companies/environments for services registry can be used:
etcd
counsul
apache zookeeper
distributeme registry
any custom solution (like in our case)
And moskito can provide some integration SPI (API) for all of this.
Default implementation (from the box) for this SPI's can use direct registration (with some keep-alive functionality) from moskito (client role) to moskito (server role) through just IP configuration.
I know that i can provide a pull request with such functionality, but i think for the first we should have a discussion about this feature.
The text was updated successfully, but these errors were encountered:
bolbat
changed the title
Moskito Inspect SPI for automatic client/server registration/resolving
SPI for automatic client/server registration/resolving (Moskito Inspect)
Jun 2, 2016
Currently we have 2 options how moskito instances could be registered in servers list in standalone moskito inspect application:
Maybe we have more options, but i didn't made deep research.
And for big and dynamic production environments where everything is deployed frequently with containers with automatic scaling (based on load) this is not working approach (i'm about static configuration in moskito-inspect.json).
And we need some SPI for moskito (client role) when each application where moskito-core+rmi_api is integrated can register self in our "private registry" through own implementation.
And also we need some SPI for moskito (server role) (in our setup this is standalone moskito-inspect war application) through what we can resolve (from our "private registry") all running moskito instances.
For different projects/companies/environments for services registry can be used:
And moskito can provide some integration SPI (API) for all of this.
Default implementation (from the box) for this SPI's can use direct registration (with some keep-alive functionality) from moskito (client role) to moskito (server role) through just IP configuration.
I know that i can provide a pull request with such functionality, but i think for the first we should have a discussion about this feature.
The text was updated successfully, but these errors were encountered: