Multiple requests about levee

[totherik]

Hey Louis,

Thanks for asking. In this case, levee doesn't hold an opinion as to how granular each breaker behaves. In the example you can see the get is wrapped, meaning all endpoints are managed using a single breaker. This is probably too coarse as different hosts and resources have significantly different SLAs, meaning one resource could trip the breaker blocking get from reaching the entire internet. (That said, it makes for a simple example).

Where I work, when used with HTTP, AFAIK we have a breaker per resource as individual endpoints within a service do varying amounts of work, have different SLAs, and may require distinctly different timeouts. Then we apply smart defaults for a given service (all endpoints), and allow configuration individual endpoints on an as needed basis. This provides granular control, but it also (via stats) gives insight into the behavior of individual endpoints, which can be useful.

I hope that helps, but if not let me know!

[jooj123]

@totherik question on this - does the path (first param to run) need to be unique for each resource in order to prevent one service from tripping a circuitbreaker on another ?