Journey to open platform for digital bank modernization. A reference implementation of BIAN to start, providing documentation and artifacts of reusable source code.
Apache License 2.0
15
stars
9
forks
source link
As a developer I expect that any service domain is available at any time and that it responds to a call. #13
As a developer, I expect that any service domain is available at any time and that it responds to a call.
Description of Problem:
Mercury framework uses knative/camel-k serverless approach, which means that if there no calls the service will be down.
that can cause delays in the response time
Potential Solutions:
is it possible to have a service up all time? at least for most frequent used
note: this problem exists only when interacting with REST API
Feature Request
As a developer, I expect that any service domain is available at any time and that it responds to a call.
Description of Problem:
Mercury framework uses knative/camel-k serverless approach, which means that if there no calls the service will be down. that can cause delays in the response time
Potential Solutions:
note: this problem exists only when interacting with REST API