Group: GitHub Softistx

Sort by:Popular▼

✓Popular✓Newest

What more than one stx library needs and nothing else: pages, coroutine primitives, the shared JSON and CloseGuard

The Ktor foundation the stx plugins are built on — the resource-lifecycle idiom, and one CORS policy shared with Spring

The MongoDB coroutine driver made reusable: a codec registry, session-aware CRUD, a cursor-paged find and GridFS

Hibernate Reactive over the Vert.x Postgres client — JPA mapping and a typed Criteria API with no thread parked on a query

Logs and traces for a Kotlin coroutine service: the current span is a CoroutineContext element, an event is a @Serializable type, and export is a background drain

Redis over Lettuce's coroutine commands — values, keys, scans and locks, without wrapping the protocol again

GraphQL for a Kotlin coroutine service: annotations, kotlinx.serialization, suspending execution over graphql-java

Message catalogues loaded once at startup, with ICU formatting, per-key fallback and Accept-Language negotiation

Schema migrations written in Kotlin: a version, a ledger and a lock, with no store in this module

Compensable workflows in Kotlin: a DSL of steps, a compensation per step, and state checkpointed after each one

AMQP over the RabbitMQ client, made suspending — publishing, consuming, and the confirm and ack rules

Kafka over the Apache clients, made suspending — typed publishers and a poll loop, serialized with kotlinx.serialization

Where the stx-migrations ledger lives: MongoDB and SQL through stx-jpa, one package each

S3-compatible object storage over the MinIO SDK — buckets, objects and presigned URLs, all suspending

A Compose Multiplatform component library: a token layer over Material 3, and motion that is on by default

MongoDB exporter for stx-telemetry: a batch is one insertMany, and retention is a TTL index rather than a job

OTLP/HTTP export for stx-telemetry, in JSON over the JDK's own HttpClient — kotlinx.serialization and no OpenTelemetry SDK

The SLF4J bridge for stx-telemetry, in both directions: third-party logs into the pipeline, or this library's signals out to an existing logback

Test-only support the stx libraries share: the backing services their integration specs talk to, declared rather than assumed

Where stx-workflow instances live: the WorkflowStore on Redis, on SQL through stx-jpa, and on MongoDB — one package each