Re: [Hawkular-dev] REST endpoints are multiplying
Not sure I understood you correctly, as I have some issues concentrating right now.
Usually rest-apis are build around the concept of
* one well known entry point
* linking of resources.
So basically there is e.g.
GET /hawkular
which returns
{
{"rel":"metrics", "url":"/metrics",
"rel":"alerts","url":/alerts",
...
}
and then on e.g. a single resource there is
{
"rel":"alerts", "url":/alerts/1234/"
}
and so on.
Like on a web page, but with links for machines.
The urls returned can be relative or also absolute. There may be some details to solve,but
the general
concept is built into the REST-way already.
Am 06.02.2015 um 16:08 schrieb John Mazzitelli
<mazz(a)redhat.com>:
I see all the components implementing REST APIs.
How will that scale if we cluster multiple components? Are we going to ask people to
install and configure a load balancer? Is there another way to make client configuration
easier? Because as I see it, unless clients are told of all the different endpoints of all
the different REST servers, how will they know where to go to talk REST to these
components? Even if we have load balancers, they will still need to know "here's
the REST URL for alerts, here's the REST URL for metrics, here's the REST URL for
inventory."
_______________________________________________
hawkular-dev mailing list
hawkular-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hawkular-dev
--
Reg. Adresse: Red Hat GmbH, Technopark II, Haus C,
Werner-von-Siemens-Ring 14, D-85630 Grasbrunn
Handelsregister: Amtsgericht München HRB 153243
Geschäftsführer: Charles Cachera, Michael Cunningham, Paul Hickey, Charlie Peters