JAVA

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

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. Correct Design of Controller and Service Principle: Thin Controller, Fat Service Controllers should only handle HTTP concerns: routing, request/response

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

Branch: feature/circuit-breaker (merged to main) Commit: 241481b Date: 2026-02-26 Library: Resilience4j 2.2.0 via Spring Cloud Circuit Breaker 3.2.0 Problem Auth-service

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

Date: 2026-02-27 Context After converting auth-service from Servlet (Spring MVC) to WebFlux, 80-90% of the code is reactive/async. But 10-20%