Bookshelf: A Guide to Building a Self-Hosted E-Book Library on Object Storage

Bookshelf: A Self-Hosted E-Book Management Tool Built on Object Storage

In the realm of personal digital asset management, collecting and organizing e-books has long been a core need for many tech enthusiasts. Recently, an open-source project called Bookshelf has garnered attention on Hacker News. It's a self-hosted e-book library application whose standout feature is that it runs directly on object storage, offering a completely new architectural approach to personal e-book collection management.

The project received 22 upvotes and several discussion threads on Hacker News. While not explosively popular, its technical design philosophy holds significant representational and discussion value within the self-hosting community.

Why Choose Object Storage as the Underlying E-Book Storage?

Traditional self-hosted e-book solutions (such as the widely popular Calibre-Web) typically rely on local file systems or mounted disks to store book files. This approach works well in single-machine scenarios but has inherent limitations in scalability, backup reliability, and cross-device access.

Bookshelf treats object storage as a first-class citizen. This means users can store their e-book files directly on S3, MinIO, or any S3-compatible object storage service.

What Is Object Storage?

Object storage is a data storage architecture that manages data as "objects," where each object contains the data itself, metadata, and a unique identifier. Unlike the hierarchical directory structure of traditional file systems, object storage uses a flat namespace and performs data operations through RESTful HTTP APIs. Amazon S3 (Simple Storage Service) is the de facto standard for object storage, and its API protocol has been widely adopted. MinIO is a high-performance open-source object storage server that is fully S3 API-compatible and is commonly used in self-hosted scenarios as a replacement for cloud-based S3 services. Object storage is particularly well-suited for storing unstructured data (such as images, videos, and documents), with a design that naturally supports horizontal scaling and high availability.

This design brings several significant advantages:

• Nearly unlimited scalability: Object storage is inherently suited for massive unstructured data storage, so users never need to worry about running out of disk space.
• Higher data durability: Mainstream object storage services typically offer multi-replica redundancy, providing far greater data reliability than a single hard drive.
• Decoupled architecture and storage: The application itself can be stateless or light-state, making it easy to deploy and migrate in container or cloud-native environments.

The Ecosystem Advantage of the S3 Protocol

The S3 protocol has become the lingua franca of object storage. Beyond AWS's native S3 service, virtually all major cloud providers (such as Alibaba Cloud OSS, Tencent Cloud COS, and Google Cloud Storage) offer S3-compatible interfaces. In the self-hosting space, open-source solutions like MinIO, Ceph's RadosGW, and SeaweedFS are also S3 API-compatible. This means applications developed on the S3 protocol have extremely high portability—users can freely switch underlying storage providers without modifying application code, thus avoiding vendor lock-in. Bookshelf's choice to build on the S3-compatible protocol leverages precisely this ecosystem advantage.

For users who already run MinIO for self-hosted object storage or rely on cloud-based S3 services, Bookshelf offers a solution that naturally fits their existing infrastructure.

The Core Value of Self-Hosted E-Book Libraries

In recent years, as people have become more concerned about data sovereignty and privacy, the self-hosted application ecosystem has continued to flourish. From Nextcloud and Immich to various media servers, users increasingly want to keep their digital assets under their own control rather than entrusting them to third-party commercial platforms.

Data Sovereignty and the Rise of the Self-Hosting Movement

Data sovereignty refers to the concept that individuals or organizations have complete control over the data they generate. In recent years, as major tech companies have experienced frequent data breaches, unilaterally modified terms of service, or even abruptly shut down services (such as Google Reader, Stadia, etc.), an increasing number of technical users have turned to self-hosted solutions. The r/selfhosted community on Reddit has over 300,000 subscribers, and the Awesome-Selfhosted project catalogs hundreds of self-deployable open-source alternatives. The core demand of this movement is: users' digital assets should not depend on any third party's goodwill but should run on infrastructure the users themselves control.

Bookshelf is a product of this trend. It enables users to:

Maintain Complete Control Over E-Book Data

All e-book files and metadata are stored in user-controlled storage, free from the risks of account binding, format lock-in, or service discontinuation associated with commercial reading platforms.

Flexible Containerized Deployment

Leveraging the decoupled nature of object storage, Bookshelf is well-suited for running in modern container orchestration environments. Cloud Native is a methodology for building and running applications that takes advantage of cloud computing, with core principles including containerization, microservices architecture, declarative APIs, and immutable infrastructure. In cloud-native architecture, applications are designed to be "stateless" or "light-state"—meaning application instances themselves don't persist business data, and all persistence needs are delegated to external services (such as databases, object storage, and message queues). This design allows applications to be destroyed and rebuilt at any time, supporting horizontal scaling, rolling upgrades, and automatic failure recovery. Container orchestration platforms like Kubernetes are designed around this philosophy, and externalizing the storage backend to object storage is one of the key strategies for achieving application statelessness.

Whether on a home NAS, personal VPS, or private cloud cluster, Bookshelf can be deployed with relative ease.

Bookshelf vs. Calibre-Web

From a positioning standpoint, Bookshelf's direct competitor is Calibre-Web and its variants.

Technical Background of Calibre-Web

Calibre is an open-source e-book management desktop application developed by Kovid Goyal, featuring powerful metadata editing, format conversion, and device synchronization capabilities. Under the hood, it uses a SQLite database to store book metadata, while book files are organized in a specific directory structure on the local file system. Calibre-Web is a web frontend built on the Calibre database, allowing users to access and manage their library through a browser and supporting the OPDS protocol for e-readers to directly fetch books. Its architectural assumption is that book files exist at locally accessible file paths, which is very convenient for NAS or single-machine deployments but requires additional file system mounting configurations (such as NFS, CIFS, or PVC) in distributed or cloud-native environments.

The core difference between the two lies in the storage abstraction layer:

Dimension	Traditional Solutions (e.g., Calibre-Web)	Bookshelf
Storage Backend	Local file system/mounted disks	Object storage (S3-compatible)
Scalability	Limited by disk capacity	Nearly unlimited
Deployment Fit	Single-machine friendly	Cloud-native/container friendly
Data Redundancy	Relies on local solutions like RAID	Relies on built-in object storage redundancy
Ecosystem Maturity	Large community, rich plugins	Early stage, features still developing

Cost Considerations for Object Storage Solutions

Object storage solutions are not without trade-offs. Compared to direct read/write on local file systems, object storage access typically involves network requests, which may incur performance overhead in latency-sensitive scenarios or frequent small-file reads.

From a cost model perspective, object storage pricing typically includes three dimensions: storage capacity fees (charged per GB/month), API request fees (PUT/GET operations charged per request), and egress traffic fees (data transferred from the storage service to the internet). Taking AWS S3 Standard storage as an example, storage costs approximately $0.023/GB/month, GET requests cost about $0.0004 per thousand, and egress traffic is approximately $0.09/GB. For e-books—a "write-infrequent, read-relatively-infrequent" scenario—storage costs are typically very low (1,000 e-books might only occupy 5-10GB, costing less than $0.25/month), but egress traffic could become the primary cost if there are many downloads. Using self-hosted object storage like MinIO completely avoids these usage-based charges, at the cost of maintaining hardware and service availability yourself.

Therefore, Bookshelf is better suited for users who already have object storage infrastructure or have higher requirements for scalability and reliability.

Use Cases and Architectural Insights

Although Bookshelf is currently a relatively early-stage project with a small community, it embodies an interesting evolutionary direction in self-hosted software design—completely separating the storage backend from application logic and embracing the cloud-native object storage paradigm.

This architectural pattern is not unique to Bookshelf. In enterprise software, many content management systems (CMS) and digital asset management (DAM) tools have long adopted object storage as their backend. Well-known open-source projects like GitLab, Harbor (container image registry), and Thanos (Prometheus long-term storage) all use S3-compatible storage as their recommended or even default persistence solution. Bookshelf's significance lies in bringing this mature enterprise-grade architectural pattern into the personal tools domain.

For developers and digital hoarders alike, such a project provides not only a practical tool but also an excellent architectural learning example: how to build a fully functional content management application around object storage.

Conclusion: A New Approach to E-Book Management Driven by Object Storage

The emergence of Bookshelf reaffirms a trend: as object storage costs decrease and adoption grows, an increasing number of applications that traditionally relied on local file systems are beginning to explore storage-first design. For users who want to break free from commercial reading platform constraints without being limited by local disk capacity, it's an option worth trying.

As an emerging open-source project, it still has room to grow in feature completeness, stability, and community support. Interested readers are encouraged to deploy and experience it firsthand, or participate in the project's development and feedback to help drive this solution toward maturity.