NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Using ReadyNAS as backend for lightweight web tools — is it reliable?
Hi everyone, I currently maintain a small web tool (for example a gratuity / end-of-service benefit calculator for users in the UAE), and I’m evaluating options to host user data, logs, JSON storage files, and backups. My ideal setup is a lightweight, always-on system without needing a full server. That’s where ReadyNAS caught my interest. Some of the things I’m considering: Using ReadyNAS to host REST APIs, static JSON or YAML config files, and backing up user session data. Ensuring data integrity and performance — especially under concurrent access. Handling firmware updates without breaking API endpoints. Syncing backups to cloud or another NAS for redundancy. A few questions for those experienced with ReadyNAS: 1. Has anyone used ReadyNAS to back a small web service or tool (not just file server)? 2. What is the maximum recommended concurrent requests for lightweight API files (JSON) on ReadyNAS? 3. Which methods have you used for version-safe firmware updates so that custom services are not lost? 4. How do you handle secure access (SSL, tokens) when serving APIs from a NAS that’s also storing private user data? If anyone’s already built similar backend or microservice setups using ReadyNAS, I’d love pointers or pitfalls to avoid. Thank you!
