[Discuss] REST API Availability based on the Availability of SM, CC and AS

[Imesh Gunaratne <im...@apache.org>]

Hi Devs,

Currently at the server startup REST API becomes available even before SM,
CC and AS are active and available. On the other hand if one of the
components becomes unavailable after starting the server API calls may fail
in the middle while trying to serve requests. The downside is, this may
cause inconsistencies in the system.

May we need to handle this properly. I would like to propose to handle this
by intoducing a request handler in the REST API which could check the
availability of SM, CC and AS on each external API call. If one of the
components are unavailable API call can be rejected. For this SM, CC and AS
can expose a service method to check the status in their SOAP services.
WDYT?

Thanks

-- 
Imesh Gunaratne

Technical Lead, WSO2
Committer & PMC Member, Apache Stratos

Re: [Discuss] REST API Availability based on the Availability of SM, CC and AS

[Imesh Gunaratne <im...@apache.org>]

A good point Udara, if we are implementing transactions we may need to
manually handle each process.

Thanks

On Sat, Feb 7, 2015 at 12:31 AM, Udara Liyanage <ud...@wso2.com> wrote:

> Hi Imesh,
>
> Say an API call to do some modifications in AS and CC. The inconsustency
> may occur either one of the components us down or an error occured. So we
> might need to handle in transactional way, all or nothing. If I am
> understanding correctly, just checking for existent may not cover 100%.
> On the other hand checking existence of the components for all the
> requests adds an overhead. If we can filter them it is helpfull. For
> instance GET requests don't need it since they does not change the state.
>



-- 
Imesh Gunaratne

Technical Lead, WSO2
Committer & PMC Member, Apache Stratos

Re: [Discuss] REST API Availability based on the Availability of SM, CC and AS

[Udara Liyanage <ud...@wso2.com>]

Hi Imesh,

Say an API call to do some modifications in AS and CC. The inconsustency
may occur either one of the components us down or an error occured. So we
might need to handle in transactional way, all or nothing. If I am
understanding correctly, just checking for existent may not cover 100%.
On the other hand checking existence of the components for all the requests
adds an overhead. If we can filter them it is helpfull. For instance GET
requests don't need it since they does not change the state.