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

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

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.

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

Series Navigation: Introduce AdventureTube Microservice Hub Part 1: Architecture Overview & Design Patterns Part 2: Development Environment & Debugging Part

1. Correct Design of Controller and Service Principle: Thin Controller, Fat Service Controllers should only handle HTTP concerns: routing, request/response

1. Backend — Implemented (2026-03-09) Status: COMPLETED — All Tests Passing Merged to main via commit 99ea583 (branch feature/kafka-job-status-sse). 42

1. Why Kafka Over Other Message Brokers AdventureTube uses Apache Kafka for asynchronous messaging between microservices. Here’s why Kafka was