Hi NocoBase team and community,
We’re excited to start using NocoBase in our office setup. We’ve deployed it with Docker and have 20 users actively working in the system.
Our use case includes storing records like:
- Purchase Orders
- Proof of Deliveries
- Invoices
- Supporting attachments (images, scanned PDFs, videos)
Each record can have multiple file attachments, and some files (especially scanned PDFs or videos) can be large — up to 20MB per file, with potentially 20+ files per record.
We’ve configured separate Docker volumes for:
- PostgreSQL (
pg_data
) - File storage (
storage_data
) - Redis (
redis_data
)
We’re currently using NocoBase’s default local file storage, but we’re planning for long-term use — potentially years of records with thousands of file uploads.
Questions:
- Can NocoBase handle large volumes of files and large individual file sizes (e.g. 25MB each) for long-term use without performance degradation?
- Is there a recommended limit to the number of files per record or total files per volume?
- Would you recommend switching to external object storage for better scalability and performance? If so, which option would you suggest for the easiest setup and integration with NocoBase? As we are new to Nocobase
- Any best practices for organizing file storage or optimizing attachment performance?
We want to ensure our system stays responsive and reliable even after storing hundreds of thousands of attachments over time.
Thanks in advance for your guidance and for the amazing work on NocoBase!