Skip to content

Initial API straw architecture.#3

Open
iparask wants to merge 3 commits into
mainfrom
feat/api
Open

Initial API straw architecture.#3
iparask wants to merge 3 commits into
mainfrom
feat/api

Conversation

@iparask

@iparask iparask commented Jun 30, 2026

Copy link
Copy Markdown
Member

This is not even close to complete. It is missing a few features, how ever I hope it shows where this is going and how I think archivist will be.

I introduce the server side endpoints. Both at post based. The archive receives a manifest, creates a unique id for it and queues it. The extract end point will be similar, but I am not sure yet about the type of data it will receive.

Storage can either be Posix or HPSS. A secondary thread will monitor the archive queue. As soon as there is something, it will pull it, create a tarball if needed and push it to the storage.

All transactions will be recorded in a local postgres, or sqlite DB. A third thread will probe the DB and based on the status of archives it will communicate with the librarian which data points are archived.

Claude is used as a help to make choices and quickly implement things that are not in my head immediately.

@iparask iparask requested review from JBorrow and tskisner June 30, 2026 19:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant