Application drivers
Choose a client by application runtime and API requirements:
| Application | Recommended client | Transport |
|---|---|---|
| Java application using JDBC | Kubling JDBC driver | Native |
| Java application using Hibernate | Kubling Hibernate dialect | Native |
| Go application | Official Go SDK | gRPC |
| Python application using SQLAlchemy or DB-API | Kubling SQLAlchemy driver | gRPC |
| Python application using the RPC API directly | Official Python package | gRPC |
| Other non-Java application | Generated client from the public protobuf contract | gRPC |
| Existing PostgreSQL-compatible client or tool | Its existing PostgreSQL driver | PostgreSQL compatibility |
Use gRPC for new non-Java applications. The PostgreSQL wire protocol remains available for existing clients and tools that require it, but it is not the recommended application integration.
Java applications that require JDBC or an ORM should use Kubling’s native JDBC transport. Java applications that do not require JDBC can also use the official generated gRPC client.
Applications upgrading their Java or native JDBC integration to 26.5 must follow the naming migration.
See Transports for the protocol boundaries and listener configuration.
Last updated on