Hi Pubudu,
On Tue, Feb 12, 2019 at 12:01 PM Pubudu Gunatilaka wrote:
> Hi,
>
> I think it is a basic need to have a health API for the microgateway. This
> is the pull model. If you take any container mgt system or any other
> system, to configure the health of the microgateway we need to
Hi,
I think it is a basic need to have a health API for the microgateway. This
is the pull model. If you take any container mgt system or any other
system, to configure the health of the microgateway we need to provide an
endpoint.
As explained above in the problem description, if the
Hi,
This will be a good addition. I'm more into a push model because of the
scalable nature of that.
I found this[1] interesting even though it's questionable what happens if
the agent stops responding. Maybe they have implemented a deadman's
switch[2].
[1]
On Tue, Feb 12, 2019 at 10:49 AM Lawshiga Thurairasasingam <
lawsh...@wso2.com> wrote:
> Hi all,
>
> I'm in the process of implementing a connector for WSO2 EI that support
> Ethereum blockchain.
>
> API: JSON-RPC API
>
> Authentication mechanism: None
>
> Ethereum is an open-source, public,
Hi Sanjeewa,
The use of pull model it's the best model to operate since container system
also supports to give availability from health check api.
Configure outside system inside gateway is tricky as we locked down the
outside system can't be change with the time . ( Different load
Hi Hasitha,
There are some constraints in creating a template for pre-defined scenarios
:
1. The user wouldn't be aware of the fact that a 3rd party dependent
library is downloaded.
2. If we are to download dependencies based on pre-defined scenarios
there are some instances where
Hi Sangeeth,
One thing we can do is to template the approach for pre-defined scenarios.
Eg: Read a file like below and user can select and download, then it go
through dependencies under the section and present as a zip/automatically
put to internal micro ESB.
Hi All,
ESB tooling requires adding of required dependencies such as *".jars"
*to *"ESB/lib"
*directory, where the user has to search for the relevant jar & download
it, copy it to the lib directory.
Due to some license constrains we can't ship & redistribute those 3rd party
jars with the
