I've been working through a list of places where Dynoxide answers differently from DynamoDB.
Badges
Badges come from GitHub once the author claims this feed.
Recent posts
every link opens the author’s post-
DynamoDB's PartiQL reads some comparisons backwards
-
Dynoxide 1.6.0 release notes
Dynoxide 1.6.0 went out on Saturday night and I forgot to write it up, so this is a couple of days late.
-
DynamoDB changed how it bills a vector read
On 9th October I pinned a test in Parity Suite that said a read of a particular DynamoDB item costs 2 read units.
-
Dynoxide 1.5.0 release notes
Dynoxide 1.5.0 is out, two days after 1.4.0. The vector fixes came out of Parity Suite, and I wrote up the billing change earlier today, so this one's just the list.
-
Dynoxide 1.4.0: clean shutdowns and JSON Lines import
Dynoxide 1.4.0 is a smaller release than 1.3.0. There's a community contribution, a new way to stop an embedded server, and another round of fixes that bring updates and scans closer to DynamoDB.