Creating a Delete Function in Spring Microservices — Real-World Step-by-Step
Goal: Create a delete function across microservices with ownership verification. Phase 1 builds the basic delete flow. Phase 2 adds […]
Goal: Create a delete function across microservices with ownership verification. Phase 1 builds the basic delete flow. Phase 2 adds […]
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%
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
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
Registration Flow POST /auth/users iOS App → AuthController → AuthService.createUser() → Google API (verifyIdToken) → Member-Service (emailDuplicationCheck) → Member-Service (registerMember)
Overview AdventureTube utilizes a backend system comprised of microservices. Each microservice is independently built as a Docker container and managed
Introduction When building the AdventureTube CI/CD pipeline, I need to address three key questions to ensure an efficient and scalable
This page is the master technical reference for the AdventureTube backend platform — a Spring Cloud microservices system deployed on