JAVA

1. Monitoring & Admin Tools All tools are accessible via Nginx Proxy Manager (PI1) with SSL. Each tool has a […]

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

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

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

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

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

Goal: Route all geo writes through Auth Service, enforce content ownership via JWT email matching, and return SSE streams for

Goal: Create a delete function across microservices with ownership verification. Phase 1 builds the basic delete flow. Phase 2 adds

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

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