ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Build a lean KrakenJS micro‑service by leveraging its module isolation, lazy loading, and routing. This guide details requirements, a minimal architecture, trust boundaries, operational checks, and failure modes that may force a redesign.
Stop dealing with fragmented traces. Learn how OpenTelemetry Context Propagation and W3C headers link microservices into a single, observable journey.
Learn how to implement true bounded contexts using JHipster microservices, focusing on database separation, trust boundaries, and operational resilience with Resilience4j.
Learn how to use Moleculer's dependency system to control service startup order and use broker.call() for reliable inter-service communication.
A custom JSON codec and worker verticles keep the Vert.x Event Bus responsive, but clustered delivery introduces silent failure modes and a hard 256 KB payload limit.
Choosing between a JHipster monolith and microservices hinges on trust boundaries, data consistency, and operational resilience. This guide walks through the decision criteria, the smallest suitable design, and concrete steps to verify security and fault tolerance.
NATS JetStream KV can store microservice state without adding Redis, but it behaves differently than a database. Understand tombstones, quorum writes, and revision checks before you deploy.
Add cross‑service visibility with Sentry’s built‑in tracing by enabling a single tracesSampleRate and letting SDKs propagate sentry‑trace and baggage headers. This note explains the smallest design, trust limits, operational checks and failure modes that shape the right sampling strategy.
Learn how to implement Redis Pub/Sub for real-time signaling. This guide covers the architecture for transient messaging, ACL security boundaries, and when to switch to Redis Streams for durability.
krakenjs
opentelemetry
jhipster
nodejs
vertx
nats
redis