It's common practice to use Databases if your application should store structured data. But for files storing each new project tries to create own bike.

Your application should implement file storage functionality: upload, store, deliver/download, clean up, make application-specific backups/restores and so on. It's not a problem for small projects, but it becomes a big deal if your project grows or you have a lot of such applications.


HFS server is an effort to provide unified File Storage solution to store and manage large collections of files.

In other words HFS server is a system which enables quick and easy development of the file-related part of your application:

  • You don't need to think where and how to store user files.
  • You don't need to transfer upload/download traffic within your application server.
  • You don't need to use application-specific procedures to backup/restore files.

Some users might already have found other framework that claims to have the same advantage, and you might want to ask what makes HFS so different from them. The answer is the philosophy where it is built on.

HFS is designed to give you the most comfortable experience both in terms of the API and the implementation from the day one. It is not something tangible but you will realize that this philosophy will make your life much easier as you read this guide and play with HFS.

Read more