How metatube-community/metatube-sdk-go works
MetaTube SDK is a metadata aggregation service and Go SDK. A client reaches the REST server, whose routes validate requests and delegate to the engine. The engine resolves a movie or actor provider, retrieves metadata or reviews, optionally processes images or translates text, and reads or writes cached results in SQLite/PostgreSQL. The tree documents broader search, image, translation, authentication, caching, and provider capabilities; only representative implementations were sampled, so uncertain internal calls are omitted.
Components 22
HTTP API
- HTTP Server
cmd/server/main.go - Route Dispatcher
route/route.go - Authentication
route/auth.go - Search Routes
route/search.go - Review Routes
route/review.go - Image Routes
route/image.go - Translation Routes
route/translate.go
Domain Orchestration
- Metadata Engine
engine/engine.go - Review Service
engine/review.go - Movie Metadata
model/movie.go - Actor Metadata
model/actor.go
Provider Acquisition
- Provider Registry
provider/factory.go - Provider Adapters
provider - HTTP Fetcher
common/fetch/fetch.go
Persistence
- Metadata Database
database/database.go - Database Management
engine/database.go
Media and Translation
- Image Processing
imageutil/register.go - Face Detection
detector/detector.go - Translation Core
translate/translate.go
Other components
- API Client
- Provider Websites
- Translation Services
Connections 24
- API Client → HTTP Server: sends requests
- HTTP Server → Route Dispatcher: serves routes
- Route Dispatcher → Authentication: authenticates
- Route Dispatcher → Search Routes: dispatches search
- Route Dispatcher → Review Routes: dispatches reviews
- Route Dispatcher → Image Routes: dispatches images
- Route Dispatcher → Translation Routes: dispatches translation
- Search Routes → Metadata Engine: queries metadata
- Review Routes → Review Service: loads reviews
- Image Routes → Metadata Engine: requests processing
- Translation Routes → Translation Core: requests translation
- Metadata Engine → Provider Registry: resolves providers
- Metadata Engine → Provider Adapters: fetches metadata
- Review Service → Provider Adapters: fetches reviews
- Provider Adapters → HTTP Fetcher: uses HTTP
- Provider Adapters → Provider Websites: scrapes sites
- Metadata Engine → Movie Metadata: builds movies
- Metadata Engine → Actor Metadata: builds actors
- Metadata Engine → Metadata Database: reads and writes
- Review Service → Metadata Database: caches reviews
- Database Management → Metadata Database: migrates schema
- Metadata Engine → Image Processing: processes images
- Image Processing → Face Detection: detects faces
- Translation Core → Translation Services: calls providers