Long running process for better database connectivity
Open
Nobody has claimed this yet.
- Dominant language
- Jupyter Notebook
- Stars
- 5
- Forks
- 10
- Avg merge
- 2d 20h
- Merged PRs (30d)
- 17
Description
apollo is designed around short running python modules, shelled out as processed from bun
As we're adding more database functionality, those short lived processes feel increasingly wasteful. It would be nice in particular to maintain connections to databases over a longer session.
So we should explore:
- Keeping all services alive and running some sort of IPC to share data (mastering this stuff would also let me drop the horrible file logging stuff)
- Keep the services short lived, but include a couple of long running services for database access. I suppose we could consider calling database from typescript and having some kind of IPC protocol to exchange data with the server
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue does not name specific files, tests, or entry points. Start by mapping how Python modules are launched from Bun and how database services currently communicate, then compare the proposed persistent-service and short-lived-service approaches. Done would require an agreed IPC and process-lifecycle design, which the issue does not yet define.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- bun, python, typescript
- Domain
- backend, databases, distributed-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100