Phoenix and DynamoDB Parity
The features that move Phoenix toward DynamoDB-style workloads: BSON documents, eventually consistent indexes, and a richer change stream.
- 1 BSON Document Support Storing schemaless documents in a Phoenix column, and reading, filtering, and updating their fields server-side.
- 2 Change Streams and Partition Lineage Why an ordered consumer needs region lineage, and how Phoenix tracks it as stream metadata in SYSTEM.CDC_STREAM.
- 3 Eventually Consistent Indexes Taking index maintenance off the write path with a CDC stream and an async consumer, so writes stay fast when a table has many indexes.