How jpcamilo/challenge_meli works
Project Type and Purpose
• This is a backend microservices solution focused on secure, efficient handling of large file uploads. It consists of two Spring-based services plus external support systems:
• file-gateway: a Spring Cloud Gateway that authenticates/authorizes requests and routes them.
• file-management: a Spring Boot reactive service that implements chunked upload, storage, metadata management.
• External components: Keycloak (OIDC/OAuth2), PostgreSQL, and optional cloud storage (GCP).
File Structure Analysis
• Top-level modules:
• file-gateway/…: contains a Spring Cloud Gateway project (pom.xml, Dockerfile, CORS/SecurityConfig, main application).
• file-management/…: contains a Spring Boot application with layered packages (config, controller, service, repository, model, exception), reactive controllers, chunked upload service, GCP storage adapter.
• Common cross-cutting concerns: security configs, application-*.yml, test suites.
• Supporting files: init.sql (DB schema), realm-export-meli.json (Keycloak realm setup).
README Insights
• Architecture summary confirms: API gateway, backend file service, Keycloak, PostgreSQL.
• Emphasis on: chunked (multipart) upload, reactive non-blocking flows, OAuth2/OIDC, extensible storage (local vs. GCP).
Essential Details to Capture
• API Gateway filters and route definitions.
• Reactive chunk upload lifecycle: receive chunk → temporary storage → metadata update → final assembly.
• Authentication handshake: client obtains token from Keycloak, then calls gateway.
• Database initialization via init.sql.
• Configuration injection for GCP storage (upload-service-key.json).