FiloraFS-Lite architecture

Request flow

HTTP request + X-API-KEY
  → ApiKeyFilter
  → FileController
  → FileService
  → local filesystem

Project structure

Lite intentionally avoids a database and persistence framework. The service validates the reported content type, creates a UUID stored filename, and reads or writes the configured filesystem directory.

com.file/
├── controller/FileController
├── dtos/FileStream
├── filter/ApiKeyFilter
└── services/FileService

Extension points

• Replace shared API-key access with application-specific authentication when required.
• Add content inspection, quotas, retention, and ownership rules.
• Keep local file tests isolated in temporary directories.
• Preserve controller paths when extending the implementation.