slashquery.com

What It Is

SlashQuery is a pluggable API Gateway that is essentially an HTTP reverse proxy. It is designed to preprocess requests through custom middleware/plugins before they reach the final microservice. The article shows a typical microservice entry-point scenario: different paths are forwarded to different upstreams, and plugins such as RequestID, WAF, CORS, and Prometheus can be chained before forwarding.

Core Capabilities

SlashQuery uses YAML files for declarative configuration, including the listen address, port, DNS resolver, request-id header, routes, upstreams, and plugins. Functionally, it supports single-binary deployment, DNS resolution with respect for upstream TTL, round-robin load balancing, accepting or rejecting requests with 405 based on HTTP Method, versioning based on the Accept Header, and wildcard path forwarding. The plugin mechanism is its core feature: third-party plugins must satisfy Go’s http.Handler interface and declare the package path and handler name in the configuration. The plugin execution order is determined by the list order in the YAML file.

Deployment and Ecosystem

SlashQuery needs to generate routes.go based on the configuration and plugins, then rebuild the binary. In other words, it is not a tool where you can simply download a universal binary and dynamically load all plugins. The build process requires a Go environment; the article mentions go >= 1.7. After cloning the GitHub project, you run make CONFIG=/path/to/slashquery.yml. It supports self-hosting and is also described as usable with Nginx via a Unix socket. On the ecosystem side, example plugins include cors, csrf, prometheus, requestid, and waf, but the documentation does not show plugin maturity, version compatibility, or community size.

Pricing and Support

The captured content does not mention pricing, commercial plans, SaaS hosting, or paid support. It can only be judged as more of a source-code-based self-hosted tool. Because there is no clear information about licensing, maintenance status, release cadence, or support channels, companies should assess the risks themselves before using it in production.

Pros, Cons, and Who It’s For

Its advantages are a lightweight architecture, straightforward configuration, and strong extensibility through Go plugins. It is suitable for small platform teams or microservice projects that are familiar with Go and want direct control over gateway logic. The downside is that plugin changes require rebuilding, making operations less convenient than mature options such as Kong, APISIX, Traefik, Envoy, and similar solutions. The documentation also lacks coverage of authentication and authorization, security hardening, monitoring deployment, and performance benchmarking.

Access from China

The article does not provide information about access from mainland China, mirrors, payment, or hosted services, so china_access can only be marked as unknown. If GitHub access is unstable, teams in China may need a proxy or use a code mirror. Alternatives to consider include Apache APISIX, Kong, Traefik, Envoy, or NGINX.