{
  "@context":[
    "https://www.w3.org/ns/activitystreams",
    {"Hashtag":"as:Hashtag"}
  ],
  "published":"2024-03-28T11:19:01.445Z",
  "attributedTo":"https://k.matthias.org/actors/relistan",
  "to":["https://www.w3.org/ns/activitystreams#Public"],
  "cc":["https://k.matthias.org/actors/relistan/followers"],
  "content":"<p>Amazon Keyspaces&nbsp; from <a href=\"https://k.matthias.org/tags/awscloud\" class=\"hashtag\" rel=\"tag\">#awscloud</a> is pretty interesting. It's a <a href=\"https://k.matthias.org/tags/Cassandra-compatible\" class=\"hashtag\" rel=\"tag\">#Cassandra-compatible</a> (with limitations) implementation on top of DynamoDB as far as I can tell. The nice thing about it is that it's serverless so you don't have the huge overhead for running a full Cassandra cluster. We are using it and so far so good. It has a few annoying limitations, though. These are the ones that I've hit:</p><ul><li>Only supports Cassandra protocol version 3</li><li>Fancy IAM auth (the default) requires special client library support. You can use user/password auth&ndash;thus supporting all libraries&ndash;but it is a bit of a faff to set up.</li><li>Only supports <em>write</em> consistency <code>LOCAL_QUORUM</code> . It does support other consistencies on <em>read</em>.</li><li>Using TTLs on a table requires that you set a custom option using a CQL <code>ALTER TABLE</code> statement. However, this custom option pisses of real Cassandra (and Scylla) which you are likely to be using for local dev. Which requires a migration workaround.</li></ul><p>If you can manage to work around that, it's pretty nice. And the price is attractive.</p>",
  "mediaType":"text/html",
  "attachment":[],
  "tag":[
      {"type":"Hashtag","name":"#awscloud","href":"https://k.matthias.org/tags/awscloud"},
      {"type":"Hashtag","name":"#Cassandra-compatible","href":"https://k.matthias.org/tags/Cassandra-compatible"}
  ],
  "type":"Note",
  "id":"https://k.matthias.org/objects/PakdE_Nr9lU"
}