vs

Amazon DynamoDB vs Manhattan

Amazon DynamoDB: AWS's serverless key-value and document store with single-digit-millisecond reads at any scale. Manhattan: Twitter's in-house, multi-tenant, eventually consistent key-value store with pluggable storage engines.

key differences

  • Only Amazon DynamoDB has transactions, secondary indexes, json, change data capture, triggers.
  • Only Manhattan has compression.
  • Amazon DynamoDB has a serverless option; Manhattan does not.

choose amazon-dynamodb for

  • +Serverless application backends on Lambda
  • +User profiles, sessions and shopping carts
  • +High-traffic e-commerce and gaming state
  • +IoT device state and metadata

best at · OLTP, Sessions, Cache

choose manhattan for

  • +Reference design for multi-tenant, multi-datacenter key-value platforms
  • +Studying pluggable storage engines and replica reconciliation

best at · OLTP, Time-series

overview
Primary model
Key-Value
Key-Value
Also supports
Document
Time-Series
Type
Managed service
Database engine
Status
Active
Active
Developer
Amazon Web Services
Twitter (now X Corp.)
First release
2012
2012
Latest version
–
–
License
ProprietaryProprietary (AWS service)
ProprietaryProprietary (internal only)
Free tier
✓
—
popularity
WhichDB Score
63.3
0.0
Rank
#14
#775
GitHub stars
–
–
Stack Overflow questions
14.3K
–
scale & guarantees
Comfortable data size
Massive (Multi-PB)
Massive (Multi-PB)
Horizontal scaling
Native
Native
Multi-region
Active active
Active active
ACID
Limited
Limited
Consistency
Strong, Eventual
Eventual, Strong
Schema
Schemaless
Schemaless
Architecture
Distributed, Serverless
Distributed, Multi primary
deployment
Self-hosted
—
—
Vendor-managed cloud
✓
—
Serverless
✓
—
Embedded
—
—
Edge
—
—
Clouds
AWS
–
capabilities
Transactions
✓
—
Joins
—
—
Secondary indexes
✓
—
Full-text search
—
—
Vector search
—
—
Geospatial
—
—
JSON
✓
—
Change data capture
✓
—
Triggers
✓
—
Stored procedures
—
—
Materialized views
—
—
TTL / expiry
✓
—
Pub/Sub
—
—
Columnar storage
—
—
In-memory
—
—
Durable persistence
✓
✓
Compression
—
✓
Encryption at rest
✓
—
Role-based access
✓
—
Time travel
✓
—
Branching
—
—
Online schema changes
—
—
Streaming ingest
✓
—
Offline sync
—
—
Runs in WebAssembly
—
—
interfaces
Query languages
DynamoDB API, PartiQL
Key-value API
Client languages
Java, Python, JavaScript, Go, C#, .NET, Rust, Ruby
–
Best for
OLTP, Sessions, Cache, Metadata
OLTP, Time-series

Amazon DynamoDB vs Manhattan: FAQ

What is the difference between Amazon DynamoDB and Manhattan?

Amazon DynamoDB: AWS's serverless key-value and document store with single-digit-millisecond reads at any scale. Manhattan: Twitter's in-house, multi-tenant, eventually consistent key-value store with pluggable storage engines. Only Amazon DynamoDB has transactions, secondary indexes, json, change data capture, triggers. Only Manhattan has compression. Amazon DynamoDB has a serverless option; Manhattan does not.

When should I choose Amazon DynamoDB over Manhattan?

Choose Amazon DynamoDB for serverless application backends on Lambda; user profiles, sessions and shopping carts; and high-traffic e-commerce and gaming state. Choose Manhattan for reference design for multi-tenant, multi-datacenter key-value platforms; and studying pluggable storage engines and replica reconciliation.

Is Amazon DynamoDB or Manhattan more popular?

Amazon DynamoDB ranks #14 on the WhichDB Score (63.3/100) and Manhattan ranks #775 (0.0/100). Popularity is not fit: check the requirements that matter for your project.

Are Amazon DynamoDB and Manhattan open source?

No. Amazon DynamoDB is proprietary, closed-source software. No. Manhattan is proprietary, closed-source software.