Filemap released to open source
Filemap has been released to open source. The library simplifies developing and deploying cloud-based applications by letting developers write their programs without hard-coding where files will be stored.
During development, configuration files, images, and web design assets might live on a developer's local machine. For production, a configuration entry can be changed and those same files can be served from a secure, automatically backed-up S3 bucket.
Virtual file mapping
Filemap provides virtual file mapping onto different storage locations. That means application code can ask for the file it needs, while Filemap handles where that file actually comes from.
That separation is useful when the same application needs different storage strategies across environments:
- Local development for fast iteration on config, images, and design assets.
- Cloud storage such as S3 for production durability and backups.
- Baked-in assets bundled into project JAR files when files should ship with the application.
- Plugin-backed storage for teams that need other storage options later.
Why it matters
Cloud applications often start simple, then quickly grow into environment-specific file handling: local folders for developers, managed buckets in production, packaged resources for deployment, and custom storage requirements for larger clients.
Filemap keeps that decision out of the application logic. Developers can build against a consistent file access layer, then change the storage target through configuration as the application moves from development to production.
Get the code
Filemap is available on GitHub: