Timeline for Pattern Matching on Request Body for Routing an HTTP Request
Current License: CC BY-SA 4.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 30, 2024 at 15:52 | comment | added | JimmyJames | @slebetman Actually, let me walk that last comment back a bit. A generalized search/query service doesn't really have much need for 'routing'. If you join two tables, which one is the 'resource'? But not being able to have multiple endpoints to help control and audit access isn't an advantage. In any event, the point here is that if you are hand-rolling 'routing' behind a URL when a simple path scheme would suffice is too clever by half, IMO. | |
| Apr 30, 2024 at 15:18 | comment | added | JimmyJames | @slebetman I don't disagree with your assertions, but I don't really think much of that aspect of GraphQL's design. I expect GraphQL to be relegated to the same waste bin as SOAP/WSDL at some point, but time will tell. That aside, the main concern with the OPs example is that it implies that admin functions are being supported through the same endpoint as non-admin activities. | |
| Apr 30, 2024 at 14:37 | comment | added | slebetman | The OP was merely wanting the request body to route the request to different models (tables, collections etc. whatever your db calls it's data set). And elasticsearch as well as JQL certainly fits the bill. With GraphQL it's even more extreme because GraphQL does not have a database at all, its 100% a proxying service with a query language that determines how to proxy the request to the appropriate data sources. Heck, I've even seen someone implement a GraphQL resolver to query the DOM in a browser. | |
| Apr 30, 2024 at 14:14 | comment | added | JimmyJames | @slebetman It seems that GraphQL does work in a SOAP way (I think this might be why I decided to mostly ignore it a while ago) but I'm not so sure about elasticsearch. | |
| Apr 30, 2024 at 14:03 | comment | added | JimmyJames | @sbebetman I'm not sure I follow. Are you suggesting that these query protocols 'direct' requests to different (internal) services based on the content of the document? | |
| Apr 30, 2024 at 2:46 | comment | added | slebetman | Also GraphQL. Or basically any query language exposed over HTTP. This also includes Elasticsearch (the engine that powers this website), Jira's custom Jira Query Language etc. | |
| Apr 29, 2024 at 15:31 | comment | added | Greg Burghardt | @Flater's answer and your second paragraph are a bull's eye for this question. | |
| Apr 29, 2024 at 15:21 | history | edited | JimmyJames | CC BY-SA 4.0 | deleted 2 characters in body |
| Apr 29, 2024 at 14:39 | history | answered | JimmyJames | CC BY-SA 4.0 |