Author name: strider

Overview Three distinct test patterns are used in the auth-service, each with different levels of Spring context loading, speed, and […]

Overview AdventureTube runs on a 3-node Raspberry Pi cluster with Nginx reverse proxy, Jenkins CI/CD, and domain-based access via *.adventuretube.net.

Functional style is how you write code — it’s a language feature. Reactive is how you handle concurrency — it’s

The Problem AdventureTube is a chain of microservice calls: Client → Gateway → Auth Service → Member Service → PostgreSQL

The Core Mechanism Reactive replaces “thread waits for result” with “register a callback, thread moves on, callback fires when result

1. Why Mixed Reactive / Non-Reactive Architecture The project originally attempted a fully reactive stack across all services, but was

1. Service Connection Pattern The first architecture decision for a microservice platform: how do services connect to each other? Everything

Overview Migrating Spring Security from the Servlet stack (Tomcat) to the Reactive stack (WebFlux/Netty) is the hardest part of a

Overview Distributed tracing for AdventureTube microservices using Micrometer Tracing + Brave + Zipkin. Zero Java code changes — Spring Boot