- Organisation
- Similarweb
- Predecessor
- Apache HBase key-value lane for precomputed traffic and engagement datasets
- Destination
- Amazon DynamoDB with bulk historical import from Amazon S3
- Workload
- Precomputed website traffic and engagement metrics served to Similarweb web applications
- Stage
- Completed HBase-to-DynamoDB migration
- Retirement status
- The HBase-backed lane was replaced; the exact HBase retirement date is not published.
- Confidence
- High
- Next trigger
- A formal HBase retirement date or material change to the DynamoDB/Firebolt split.
Programme context
Similarweb replaced its HBase-backed predictable-access data lane with DynamoDB while retaining Firebolt for separate analytics workloads.
Why this matters: The record identifies a named organisation, an explicit predecessor and destination platform, and a bounded workload and lifecycle stage.
Migration timeline
| Date or stage | Milestone | What changed | Evidence status |
|---|---|---|---|
| Architecture split | Migration milestone | Similarweb separated predictable-access key-value workloads from dynamic analytics. | Source-stated design |
| Production replacement | Migration milestone | The HBase-backed lane was replaced by DynamoDB. | Source-stated completion |
| 16 Jun 2026 | Migration milestone | The technical account was published. | Dated primary evidence |
Workload migration matrix
| Workload | Predecessor | Destination | Status by 23 Jul 2026 |
|---|---|---|---|
| Precomputed website traffic and engagement metrics served to Similarweb web applications | Apache HBase key-value lane for precomputed traffic and engagement datasets | Amazon DynamoDB with bulk historical import from Amazon S3 | Completed HBase-to-DynamoDB migration |
Implementation and architecture
- Bulk historical data was imported from Amazon S3.
- Scheduled batches ingest approximately seven billion records per table.
- Firebolt remains a separate analytics platform.
Known unknowns and contradictions
- The exact production cutover date.
- The exact HBase retirement date.
- Residual HBase usage outside the named lane, if any.
No missing fact is inferred to broaden the source-supported migration claim.
PlatformTrace analysis
The migration concerns the named key-value lane. Firebolt remains in use for dynamic OLAP queries, so this is not an all-platform DynamoDB claim.
Performance, cost, uptime and operational outcomes remain attributed source claims unless independently stated otherwise.
Evidence ledger
- AWS Database Blog, 16 June 2026
Similarweb R&D leadership and AWS describe the HBase source, DynamoDB target, 255 TB-plus datasets and completed post-migration architecture.
Corrections and updates
23 July 2026 — Initial Verified dossier published from the complete five-lane overnight intake and corrected central adjudication. Later milestones will be appended rather than silently replacing this state.