Group: GitHub GOKU Kakarot97

Sort by:Popular▼

✓Popular✓Newest

Event loops, sockets, pipeline, codecs and TLS: the base the protocol modules build on

HTTP/1.1, HTTP/2 (HPACK) and HTTP/3 server and client, WebSocket (RFC 6455) and Server-Sent Events

The interfaces the PostgreSQL and MySQL clients share (SqlPool, SqlClient, SqlResult, SqlRow, SqlException): code written against them runs on either database

gRPC server and client

Small, fast, dependency-free logging: lock-free asynchronous ring buffer, chain of stages (filter, enrich, append), handlers registered per level, structured fields, line and JSON output, rolling files, a System.Logger backend; no lookups, no remote ...

QUIC v1 server (experimental)

AMQP 0-9-1 client for RabbitMQ

Elasticsearch / OpenSearch client over the Hydrangea HTTP client: documents, search, scroll, bulk with a batching indexer, node failover, a small strict JSON reader and writer

Kafka client: producer with batching, consumer with consumer groups, minimal admin; one event loop, no dependencies

MetricsSink implementation for Micrometer (Prometheus, OTLP, Datadog, JMX ... through any MeterRegistry).

MongoDB client (OP_MSG wire protocol, BSON): pipelined commands over shared connections, SCRAM-SHA-256/SHA-1, TLS, cursors, records in and out, no third-party dependency

MQTT 3.1.1 and 5 client (TCP, TLS, WebSocket)

MySQL client (wire protocol): event-loop driven, pipelined commands, prepared statement cache (binary protocol), caching_sha2_password and mysql_native_password, a small pool

TraceSink that exports the framework's spans to an OpenTelemetry collector (or Jaeger, Tempo ...) over OTLP, gRPC or HTTP/protobuf, with the framework's own gRPC and HTTP clients and a hand-written protobuf encoder: batching, a bounded queue, OTEL_* ...

Small, modern non-blocking network framework on top of Java NIO: a core, and protocol modules built on it

PostgreSQL client (wire protocol v3): one multiplexed connection with automatic pipelining, prepared statement cache, SCRAM-SHA-256, a small pool

Redis client (RESP2 and RESP3): one multiplexed connection with automatic pipelining, pub/sub, transactions, scripts