Realm自托管与Realm Cloud选型咨询：植物学家APP存储同步方案

Great question! Let’s break this down based on your specific use case—offline photo capture with post-capture sync, plus the 7,500 users and 20GB storage per user (that’s 150TB total storage) you’re planning for.

Core Decision Factors #

Both options support offline-first workflows and sync, so the choice boils down to operational overhead, cost, and flexibility.

Realm Cloud Pros & Cons #

• Pros:
  • Zero infrastructure hassle: Realm handles all server maintenance, scaling, backups, security patches, and uptime. This is a game-changer if your team’s focus is building botanist-specific features (like plant identification, field note integration) rather than DevOps work.
  • Fast setup: You can get sync up and running in hours without worrying about server deployment or configuration.
• Cons:
  • Prohibitive long-term cost: 150TB of storage in Realm Cloud will be extremely expensive. Pricing ties to storage, active users, and sync traffic—all of which will scale with your user base and photo volume, making this a costly choice over time.
  • Limited customization: You can’t tweak server settings, integrate with niche academic tools, or optimize storage for large photo files as freely as with self-hosted.

Realm Self-Hosted Pros & Cons #

• Pros:
  • Cost control: You can use cloud providers (like AWS, GCP, or Azure) for storage and compute, which are far cheaper than managed Realm Cloud pricing for large-scale storage. A smart tweak here: store photos in a dedicated object storage service (S3-compatible) and use Realm only for metadata (photo tags, user data, sync state)—this cuts costs and boosts performance drastically.
  • Full flexibility: You can customize server settings, integrate with internal academic systems, enforce strict data compliance rules (critical if your app handles sensitive botanical research data), and optimize sync workflows for your exact use case.
• Cons:
  • Operational overhead: Your team will need to handle server deployment, scaling, backups, monitoring, security updates, and sync server maintenance. If you don’t have DevOps experience on the team, this could pull focus away from building app features.
  • Longer initial setup: Getting a self-hosted Realm sync cluster up and running properly takes more time than spinning up Realm Cloud.

Final Recommendation #

• Choose Realm Cloud if:
  • Your team has no DevOps resources and wants to focus 100% on app functionality.
  • Short-term speed-to-market is more important than long-term cost.
• Choose Self-Hosted Realm if:
  • You have (or can hire) DevOps support, or are comfortable managing infrastructure.
  • Long-term cost efficiency is a top priority.
  • You need custom integrations, compliance controls, or storage optimizations for large photo files.

A quick bonus tip: No matter which option you pick, avoid storing raw photo files directly in Realm objects. Using dedicated object storage for photos and Realm for metadata keeps your database lightweight and sync fast—perfect for offline field use by botanists.

内容的提问来源于stack exchange，提问作者Filipe Correia