4 ms·

Btw, we've adopted the OpenAPI parser from Mesh. The latest version allows you to use it already. Open Telemetry is almost done, will probably be released tomor

Btw, we've adopted the OpenAPI parser from Mesh. The latest version allows you to use it already. Open Telemetry is almost done, will probably be released tomorrow. What else are you missing?

morbicer 4y ago
Nice! You guys are crazy productive and responsive! What I like from Mesh is also some "tidying" utilities like renaming transforms https://the-guild.dev/graphql/mesh/docs/transforms/rename https://the-guild.dev/graphql/mesh/docs/transforms/rename I guess some error masking/customization can be done with your hooks but I haven't played with it yet. When .wundergraph/generated/wundergraph.schema.graphql is getting generated and there are some errors it can be harder to debug this (or I don't know how to do it properly) so I resorted to putting console.logs to places like node_modules/graphql/language/lexer.js Rate limiting per user can be nice, but not that important, I can live with broader limiting on ingress level.
- jensneuse 4y ago
  I'd suggest you join our discord if you haven't done yet. https://WunderGraph.com/discord https://WunderGraph.com/discord Id you're open to it, please book a meeting with me after next week, I'm on vacation, and we'll discuss what's missing for you and we'll make it work if it makes sense. https://WunderGraph.com/meet/jensneuse https://WunderGraph.com/meet/jensneuse
  - morbicer 4y ago
    Thanks Jens, I will get in touch.
- therpeterson 4y ago
  We did run into that in v0.8 and just submitted a patch to resolve what was causing our issues in one case, in another - we just download Open API spec and edited out offending complexity. For more context, our deciding factor was that mesh and other tools that look the same didn't come with the things like Automatic Retry and pre/post hooks that run in an efficient way as they do with WunderGraph. We decided that the small up-from cost of cleaning up a OpenAPI spec from a static config was worth the stability and flexibility we got from using WG. When you say serverless, do you mean running as a Cloud Function? With WunderGraph cloud you can deploy it as serverless, just as an FYI. We deployed serverlessly in our own IaC setup but cloud wasn't out yet.
  - morbicer 4y ago
    Manually cleaning specs is something I would like to avoid, our oas are generated from code so they would have to be re-cleaned after every endpoint addition/change. Great to hear reasons why you picked WG over Mesh, there's not many resources online that compares these next-gen gateways. Yes by serverless I mean AWS Lambdas, Cloudflare Workers etc. I am leaning towards deploying in k8s where rest of the stack is but it's nice to have the flexibility.
    - therpeterson 4y ago
      Yeah, we started going the k8s route and after burning about 90K with a partially working setup - we found WunderGraph trying to remove complexity of a Service Mesh, and API Gateway, etc. I get not wanting to manually adjust the OpenAPI Spec - curious what the offending code is as we've pulled in quite a few larger OpenAPI spec's without issue. I wonder if there's a #ref / definitions case that's unhandled.
  - deleted 4y ago
    [deleted]

Btw, we've adopted the OpenAPI parser from Mesh. The latest version allows you to use it already. Open Telemetry is almost done, will probably be released tomorrow. What else are you missing?

morbicer 4y ago

Nice! You guys are crazy productive and responsive! What I like from Mesh is also some "tidying" utilities like renaming transforms https://the-guild.dev/graphql/mesh/docs/transforms/rename https://the-guild.dev/graphql/mesh/docs/transforms/rename I guess some error masking/customization can be done with your hooks but I haven't played with it yet. When .wundergraph/generated/wundergraph.schema.graphql is getting generated and there are some errors it can be harder to debug this (or I don't know how to do it properly) so I resorted to putting console.logs to places like node_modules/graphql/language/lexer.js Rate limiting per user can be nice, but not that important, I can live with broader limiting on ingress level.

jensneuse 4y ago
I'd suggest you join our discord if you haven't done yet. https://WunderGraph.com/discord https://WunderGraph.com/discord Id you're open to it, please book a meeting with me after next week, I'm on vacation, and we'll discuss what's missing for you and we'll make it work if it makes sense. https://WunderGraph.com/meet/jensneuse https://WunderGraph.com/meet/jensneuse
- morbicer 4y ago
  Thanks Jens, I will get in touch.
therpeterson 4y ago
We did run into that in v0.8 and just submitted a patch to resolve what was causing our issues in one case, in another - we just download Open API spec and edited out offending complexity. For more context, our deciding factor was that mesh and other tools that look the same didn't come with the things like Automatic Retry and pre/post hooks that run in an efficient way as they do with WunderGraph. We decided that the small up-from cost of cleaning up a OpenAPI spec from a static config was worth the stability and flexibility we got from using WG. When you say serverless, do you mean running as a Cloud Function? With WunderGraph cloud you can deploy it as serverless, just as an FYI. We deployed serverlessly in our own IaC setup but cloud wasn't out yet.
- morbicer 4y ago
  Manually cleaning specs is something I would like to avoid, our oas are generated from code so they would have to be re-cleaned after every endpoint addition/change. Great to hear reasons why you picked WG over Mesh, there's not many resources online that compares these next-gen gateways. Yes by serverless I mean AWS Lambdas, Cloudflare Workers etc. I am leaning towards deploying in k8s where rest of the stack is but it's nice to have the flexibility.
  - therpeterson 4y ago
    Yeah, we started going the k8s route and after burning about 90K with a partially working setup - we found WunderGraph trying to remove complexity of a Service Mesh, and API Gateway, etc. I get not wanting to manually adjust the OpenAPI Spec - curious what the offending code is as we've pulled in quite a few larger OpenAPI spec's without issue. I wonder if there's a #ref / definitions case that's unhandled.
- deleted 4y ago
  [deleted]