3.2. Specialized and Emerging Data Stores

💡 First Principle: Beyond the "big four" (S3, Redshift, DynamoDB, RDS/Aurora), AWS offers purpose-built databases for specialized access patterns. Unlike general-purpose databases that handle many workloads adequately, these services are optimized for specific patterns — search, graph traversal, wide-column, caching, and vector similarity — and outperform general-purpose alternatives by orders of magnitude within their domain.

The exam doesn't test these specialized services as deeply as the core four, but it does test whether you can recognize when they're the right choice. When a question describes full-text search with relevance ranking, OpenSearch is the signal. Graph relationships between entities? Neptune. Sub-millisecond key-value cache? MemoryDB. The v1.1 update also introduced vector databases and open table formats — newer topics that are likely to appear on current exams.

What happens when you try to force a general-purpose database into a specialized role? Imagine building a full-text search engine on top of DynamoDB: you'd need to implement tokenization, inverted indexes, relevance scoring, and fuzzy matching yourself. OpenSearch does all of this natively, with millisecond query latency on billions of documents.