vs

Amazon DynamoDB vs Espresso

Amazon DynamoDB: AWS's serverless key-value and document store with single-digit-millisecond reads at any scale. Espresso: LinkedIn's internal, MySQL-backed distributed document store that serves as source of truth for its core data.

key differences

  • Amazon DynamoDB is primarily a key-value database; Espresso is document.
  • Only Amazon DynamoDB has triggers, ttl / expiry, encryption at rest, role-based access, time travel.
  • Only Espresso has full-text search, online schema changes.
  • Amazon DynamoDB has a serverless option; Espresso 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 espresso for

  • +Studying how a large social network built its primary document store
  • +Reference design for MySQL-backed sharded document services with CDC
  • +Background for systems such as Helix, Databus and Kafka-based CDC

best at · OLTP, Content

overview
Primary model
Key-Value
Document
Also supports
Document
–
Type
Managed service
Research prototype
Status
Active
Active
Developer
Amazon Web Services
LinkedIn
First release
2012
2012
Latest version
–
–
License
ProprietaryProprietary (AWS service)
ProprietaryProprietary (LinkedIn internal)
Free tier
✓
—
popularity
WhichDB Score
63.3
0.0
Rank
#14
#729
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
Read replicas
ACID
Limited
Limited
Consistency
Strong, Eventual
Strong, Eventual
Schema
Schemaless
Flexible
Architecture
Distributed, Serverless
Distributed, Primary replica
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
REST resource URIs (key and collection lookups), Secondary-index queries
Client languages
Java, Python, JavaScript, Go, C#, .NET, Rust, Ruby
Java
Best for
OLTP, Sessions, Cache, Metadata
OLTP, Content

Amazon DynamoDB vs Espresso: FAQ

What is the difference between Amazon DynamoDB and Espresso?

Amazon DynamoDB: AWS's serverless key-value and document store with single-digit-millisecond reads at any scale. Espresso: LinkedIn's internal, MySQL-backed distributed document store that serves as source of truth for its core data. Amazon DynamoDB is primarily a key-value database; Espresso is document. Only Amazon DynamoDB has triggers, ttl / expiry, encryption at rest, role-based access, time travel. Only Espresso has full-text search, online schema changes.

When should I choose Amazon DynamoDB over Espresso?

Choose Amazon DynamoDB for serverless application backends on Lambda; user profiles, sessions and shopping carts; and high-traffic e-commerce and gaming state. Choose Espresso for studying how a large social network built its primary document store; reference design for MySQL-backed sharded document services with CDC; and background for systems such as Helix, Databus and Kafka-based CDC.

Is Amazon DynamoDB or Espresso more popular?

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

Are Amazon DynamoDB and Espresso open source?

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