6 ms·
I don't see a problem allowing a generic GraphQL handler. It's just that I don't like the approach of allowing arbitrary queries from clients you cannot control
by jensneuse 6y ago
I don't see a problem allowing a generic GraphQL handler. It's just that I don't like the approach of allowing arbitrary queries from clients you cannot control. If this use case has a lot of demand I don't think I wouldn't support it. I'd just rather implement a seamless developer experience for code generation so you don't really want to not use it and lose the benefits.
- sradman 6y agoI think we are on the same page. From my perspective, arbitrary queries are a vector for a Denial of Service event (both intentional and accidental). This has long been one of the use cases for Stored Procedures in SQL; restrict the public interface to guard against expensive queries (large scans and sorts). Faceted Search [1] may be a counter-example but I suspect that these interfaces are implemented at least partially with Full Text Search indexes rather than purely dynamic GraphQL/SQL. It might be a useful exercise to prototype an online shopping site using WunderGraph. [1] https://en.wikipedia.org/wiki/Faceted_search https://en.wikipedia.org/wiki/Faceted_search
- jensneuse 6y agoLet me know how I can help you get up to speed. Would love to get in touch!