Group: GitHub Nacode Studios

Sort by:Popular▼

✓Popular✓Newest

Spring Boot auto-configuration for Kdrant, the coroutine-first Kotlin client for the Qdrant vector database. Adds `kdrant.*` configuration properties and exposes a ready-to-inject QdrantClient bean.

The opt-in gRPC engine for Kdrant, the coroutine-first Kotlin client for the Qdrant vector database. REST remains the default; reach for this when throughput or streaming is the bottleneck.

Default REST/Ktor engine for Kdrant, the coroutine-first Kotlin client for the Qdrant vector database: a small, pure-Kotlin HTTP transport with no gRPC, Netty, or protobuf. This is the module to depend on to use Kdrant.

Default REST/Ktor engine for Kdrant, the coroutine-first Kotlin client for the Qdrant vector database: a small, pure-Kotlin HTTP transport with no gRPC, Netty, or protobuf. This is the module to depend on to use Kdrant.

Default REST/Ktor engine for Kdrant, the coroutine-first Kotlin client for the Qdrant vector database: a small, pure-Kotlin HTTP transport with no gRPC, Netty, or protobuf. This is the module to depend on to use Kdrant.

Default REST/Ktor engine for Kdrant, the coroutine-first Kotlin client for the Qdrant vector database: a small, pure-Kotlin HTTP transport with no gRPC, Netty, or protobuf. This is the module to depend on to use Kdrant.

Default REST/Ktor engine for Kdrant, the coroutine-first Kotlin client for the Qdrant vector database: a small, pure-Kotlin HTTP transport with no gRPC, Netty, or protobuf. This is the module to depend on to use Kdrant.

Default REST/Ktor engine for Kdrant, the coroutine-first Kotlin client for the Qdrant vector database: a small, pure-Kotlin HTTP transport with no gRPC, Netty, or protobuf. This is the module to depend on to use Kdrant.

Default REST/Ktor engine for Kdrant, the coroutine-first Kotlin client for the Qdrant vector database: a small, pure-Kotlin HTTP transport with no gRPC, Netty, or protobuf. This is the module to depend on to use Kdrant.

Default REST/Ktor engine for Kdrant, the coroutine-first Kotlin client for the Qdrant vector database: a small, pure-Kotlin HTTP transport with no gRPC, Netty, or protobuf. This is the module to depend on to use Kdrant.

A JVM-only conformance suite for custom MatchGuards in Kmemo, the Kotlin Multiplatform semantic cache for LLM calls. The properties every guard must satisfy, plus the labelled corpora and the confusion matrix the built-in guards are measured with.

A JVM-only Ktor server plugin for Kmemo, the Kotlin Multiplatform semantic cache for LLM calls. Makes a SemanticCache available to route handlers, with guards against false cache hits.

A JVM-only caching ChatModel wrapper for LangChain4j, backed by Kmemo, the Kotlin Multiplatform semantic cache for LLM calls, with guards against false cache hits.

A JVM-only Micrometer MeterBinder for Kmemo, the Kotlin Multiplatform semantic cache for LLM calls. Reports hit rate, per-reason and per-guard miss counters, and embed/search/verify latency, in the registry your app already runs.

A JVM-only OpenTelemetry adapter for Kmemo, the Kotlin Multiplatform semantic cache for LLM calls. Emits metrics and a span per lookup with a child per stage, under a proposed set of semantic-convention attributes for semantic caches.

A JVM-only SLF4J CacheListener for Kmemo, the Kotlin Multiplatform semantic cache for LLM calls. One structured log line per hit, miss, write and eviction, with prompt redaction on by default.

A JVM-only caching Advisor for Spring AI's ChatClient, backed by Kmemo, the Kotlin Multiplatform semantic cache for LLM calls, with guards against false cache hits.

JVM-only Spring Boot auto-configuration for Kmemo, the Kotlin Multiplatform semantic cache for LLM calls. Gives you a SemanticCache bean from your Embedder, configured under the 'kmemo' properties prefix.

A persistent CacheStore for Kmemo that builds on every target kmemo-core does: an append-only journal over a memory-resident index, for phones, desktops and edge deployments that start cold on every launch.

A persistent CacheStore for Kmemo that builds on every target kmemo-core does: an append-only journal over a memory-resident index, for phones, desktops and edge deployments that start cold on every launch.