Conversation

Notices

1. Embed this notice
   洪 民憙 (Hong Minhee) (hongminhee@todon.eu)'s status on Thursday, 14-Mar-2024 18:02:04 JST 洪 民憙 (Hong Minhee)

   in reply to

   • marius

   @mariusor Thanks you for advice!

   • Embed this notice
     marius (mariusor@metalhead.club)'s status on Thursday, 14-Mar-2024 18:02:06 JST marius

     in reply to

     @hongminhee I think KV stores are the way because IRIs generally partition nicely by hosts. If you use a human readable IRI generation schema (eg: example.com/actors/name instead of example.com/70b5b164-2093-4c98-97e2-bc0ff49f61d0) then it partitions and queries even better.

     My simplest storage option is basically just a directory tree on disk, but that's not really meant for production use. :D

   • Embed this notice
     marius (mariusor@metalhead.club)'s status on Thursday, 14-Mar-2024 18:02:07 JST marius

     @hongminhee the simplest way to store ActivityPub objects is in a KV store because mainly you already have the keys: the object IRIs, and the value in the form of the raw JSON.

     My advice: start with KV and plan for multiple storage options as a nice to have.

     In my case the sqlite storage is used mainly as a KV store anyway, with generated columns for query convenience.