Organisation rule: the database connection budget — write it into the contributing rules and each product contract
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- postgresql
- Domain
- databases
Research direction
Start by reading this repository’s contributing rules and product contract files, then review the proposed connection budget and deployment costs in the issue. The requested change is to document the pool and database rules in those files; it is ready to proceed only after Oussama approves the proposal.
Written by the indexing model from the issue text.
Description
After the Orochia connection incident (krizaka/orochia#104 one pool per process, #106 the budget: (instances + 1) × (pool + LISTEN) + jobs + admin ≤ 70 % of the slots), a rule for every product of the org: one pool per process, a sized pool, the budget written in each AGENTS.md, a managed database with a pooler in production. The proposal (dev: no cost; production: a managed 1 GB database + pool, about CA$21 a month at launch) waits for Oussama's approval; then a session writes it into this repository's contributing rules and each product contract.
Tracked on the Krizaka Roadmap.
- Dominant language
- No language data
- Stars
- 0
- Forks
- 0
- Avg merge
- 1h 52m
- Merged PRs (30d)
- 26
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing 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.
More from krizaka/.github
-
area:growth owner:oussama priority:later product:krizaka product:site type:design
Difficulty 1/5 Under an hour Newbie friendliness 68/100
krizaka/.github#15 · 2 comments ·
Maintainers usually reply within 1 day
-
area:architecture area:backend priority:next product:krizaka type:feature
Difficulty 5/5 Over a week Newbie friendliness 12/100
krizaka/.github#67 · 1 comment ·
Maintainers usually reply within 1 day
-
area:architecture area:compliance priority:next product:krizaka type:feature
Difficulty 5/5 Over a week Newbie friendliness 8/100
krizaka/.github#66 · 1 comment ·
Maintainers usually reply within 1 day
-
area:architecture area:infra priority:next product:krizaka type:feature
Difficulty 5/5 Over a week Newbie friendliness 15/100
krizaka/.github#65 · 1 comment ·
Maintainers usually reply within 1 day
-
priority:next
Difficulty 5/5 Over a week Newbie friendliness 8/100
krizaka/.github#64 · 2 comments ·
Maintainers usually reply within 1 day
Similar issues
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
OpenIntegrationEngine/engine#496 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Maintainers usually reply within 4 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
tursodatabase/turso#10054 ·
Maintainers usually reply within 1 day
-
Connection.prototype.bulkWrite() with ordered: false resolves null when a write failsPossibly taken @maxymlyskov claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Automattic/mongoose#16601 ·
Maintainers usually reply within 2 days
-
Filters: ?field:ne=null matches NULL rows instead of non-NULL onesPossibly taken @rshdhere claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Netflix/metaflow-service#504 ·