Search Indexes, Object Storage, and CDNs

Search engines build inverted indexes and other structures for text relevance, filtering, facets, and ranking. They are usually derived views rather than the authoritative record store. Updates may be eventually consistent, so a newly created record may not appear immediately in search.

Object storage is designed for large blobs such as images, videos, archives, and backups. Store metadata and ownership in a database and keep the blob in object storage; use signed URLs or controlled gateways for uploads and downloads. Validate file type, size, ownership, and scanning status rather than trusting a filename.

A CDN caches suitable static or cacheable content at edge locations. Versioned asset names make long cache lifetimes safer. For private content, use authorization-aware signed URLs and carefully scoped expiration; never assume that an obscure URL is access control.

Key Takeaways
  • Search indexes are often derived and eventually consistent.
  • Object storage is a better fit than database rows for large blobs.
  • Signed URLs need narrow permissions and expiry.