-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Plugin support #104
Comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
IMO it makes a lot of sense for agogos to have plugin support, probably mostly for custom directives.
To properly support plugins, we should come up with a way to support all types of custom directives - both runtime directives and compile time directives (#9)
The trouble here is, that runtime directives run on the gateway which is written in Go, and compile-time directives probably should run on the registry after we stitch the schemas together, which runs on NodeJS.
WASM could work for both. Im slightly worried of running WASM on the hot path, but we can look into its performance implications.
Another options could be rewriting the registry in Go, which could also help with other things like better registry validation of schemas and less polyglotting needed to work on Agogos.
The text was updated successfully, but these errors were encountered: