A cloud-native database gateway and framework that proxies and extends database traffic with plugins for caching, security, and observability.
GatewayD is a cloud-native database gateway and framework that sits between database servers and clients, proxying all their communication. It allows developers to inspect, transform, and secure database traffic through a plugin-based architecture, enabling features like query caching, SQL injection detection, and observability. It solves the problem of limited control and visibility in database interactions by providing a middleware layer similar to API gateways but for databases.
Developers and DevOps engineers building data-driven applications who need enhanced control, security, and observability over database traffic, especially in cloud-native environments.
Developers choose GatewayD for its database-agnostic, plugin-based extensibility, allowing custom functionality without modifying database servers. Its cloud-native design, built-in observability, and security features like SQL injection prevention provide a robust alternative to traditional database proxies.
database gateway for building data-driven applications
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Built as containerized, stateless, and observable, it fits modern infrastructure like Kubernetes, as highlighted in its cloud-native principles.
Supports custom plugins via Go SDK and includes built-in ones for caching and SQL injection detection, allowing deep customization without server modifications.
Provides built-in logging, metrics, and tracing, making it easy to monitor database traffic comprehensively, as emphasized in its features.
Manages multiple databases and clients within a single instance, enabling efficient resource use in shared environments.
While the core is protocol-agnostic, NoSQL support is still pending, and specific database functionality relies on plugins that may be experimental or require custom development.
Requires detailed global and plugin configuration, which can be time-consuming, especially for teams new to middleware or plugin ecosystems.
Some plugins, like the JS plugin, are labeled experimental, indicating potential instability or incomplete features that may not be production-ready.