Re:Amazon API Gateway – Build and Run Scalable Application B...
by jacques_chester on Friday July 10, 2015 @01:09AM
(#9862407)
That's the easy case.
A harder case is when you have a "service" layer which also has a large collection of queries at various levels of abstraction.
These map poorly into resources, where you want a single level of abstraction per resource. And they map badly to legacy consumers, who've grown comfortable to having a collection of special knobs and dials perfectly shaped for their exact needs.
A harder case is when you have a "service" layer which also has a large collection of queries at various levels of abstraction.
These map poorly into resources, where you want a single level of abstraction per resource. And they map badly to legacy consumers, who've grown comfortable to having a collection of special knobs and dials perfectly shaped for their exact needs.