Hi Samantha,
On 24.6.2011 0:08, Samantha Berger wrote:
> Hi Folks,
>
> I am trying to build an infrastructure of restful services in an
> hierarchical way. In current scenario, there are five services e.g. s1, s2,
> s3, s4, and s5 which are deployed on respective (independent) jersey
> servers/machines, even they have the same kind resource interface (exposing
> some application). They are related in a manner like s5 and s4 are children
> of s3, while s3 and s2 are the children of s1 (the root).
>
> My solution (could be very naive): maintaining a hierarchy by telling each
> service about its parent, likewise the parent would be aware of its children
> (through some configuration files).
>
> Having said that it can be naive because of dealing with the failure of
> intermediate service (s2) would ultimately make the s4 and s5 unreachable,
> although they are running.
I guess I am missing more context. In what sense are these related (i.e.
what does it mean for one to be a child of the other)? Do s4 and s5 need
resources of its parents to work properly? If so, then it seems natural
they won't work. E.g. if I have a mashup of GoogleMaps with my photo
sharing service, and one of those services is down, obviously my mashup
service won't work, or the functionality will be very limited.
Martin