Episode 3: Delete Story (with Screenshot Cleanup)
This documents the Delete Story flow — a synchronous pipeline that deletes screenshots from MinIO S3, then removes the AdventureTubeData […]
This documents the Delete Story flow — a synchronous pipeline that deletes screenshots from MinIO S3, then removes the AdventureTubeData […]
This documents the Chapter Screenshot Service — an async pipeline that extracts screenshots from YouTube videos at each chapter timestamp
This documents the complete request flow when an iOS user publishes a story (geo data) through the AdventureTube microservice architecture.
This page documents all communication flows between the iOS app and the AdventureTube backend microservices and will be posted as
1. Monitoring & Admin Tools All tools are accessible via Nginx Proxy Manager (PI1) with SSL. Each tool has a
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
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.