Open Source Database Clients

Golang SQL database client for ClickHouse. There are two version of this client, v1 and v2, available as separate branches. v1 is now in a state of maintenance, we will only accept PRs for bug and security fixes. Uses ClickHouse native format for optimal performance. Utilizes low level ch-go client for encoding/decoding and compression (versions >= 2.3.0). Supports native ClickHouse TCP client-server protocol. Compatibility with database/sql (slower than native interface!). Database/sql supports http protocol for transport. (Experimental). Marshal rows into structs (ScanStruct, Select). Unmarshal struct to row (AppendStruct). Connection pool Failover and load balancing. Bulk write support (for database/sql use begin->prepare->(in loop exec)->commit). AsyncInsert, named and numeric placeholders support. LZ4/ZSTD compression support. External data.

ioredis is a robust, full-featured Redis client that is used in the world's biggest online commerce company Alibaba and many other awesome companies. Full-featured. It supports Cluster, Sentinel, Streams, Pipelining and of course Lua scripting & Pub/Sub (with the support of binary messages). High performance. Delightful API. It works with Node callbacks and Native promises. Transformation of command arguments and replies. Transparent key prefixing. Abstraction for Lua scripting, allowing you to define custom commands. Support for binary data. Support for TLS. Support for offline queue and ready checking. Support for ES6 types, such as Map and Set. Support for GEO commands. Support for Redis ACL. Sophisticated error handling strategy. Support for NAT mapping. Support for autopipelining. ioredis supports all of the scripting commands such as EVAL, EVALSHA and SCRIPT.

DBD2 inserts database records from TCP input. It is a companion project to Syslgod2 and an application in its own right. It ships with a backgrounding client for generic use. The client sends whatever information the user puts on the command-line to the back-end daemon via TCP. Upon successful transmission, the client exits. On failure, it backs off and retries until its life-time timer expires. The back-end daemon accepts data from Syslogd2 or its own client and inserts that data (and envelope information) into one or more databases using MySql client library or dbi drivers (also on SourceForge). The client needs no configuration (all input is via command-line). It is intended for hosts to make database entries without needing database client or interface code. Syslogd2 integration allows DBD2 to act as Syslogd2's database back-end for MySql and other databases supported by the dbi drivers. Original purpose was to track Linux cluster job status but other uses exist.

This is a client/server project. Server part is store information about logins in SQL database. Client part it\'s NSS-module for glibc. Client integrates into any program, which use standard getpw.../getgr...