nexo/services/core/server/channels
2026-05-30 08:01:21 +09:00
..
api4 chore(upstream): refresh core snapshot 2026-05-30 08:01:21 +09:00
app chore(upstream): refresh core snapshot 2026-05-30 08:01:21 +09:00
audit Initial nexo monorepo migration 2026-05-26 10:42:29 +09:00
db chore(upstream): refresh core snapshot 2026-05-30 08:01:21 +09:00
doc/help Initial nexo monorepo migration 2026-05-26 10:42:29 +09:00
jobs chore(upstream): refresh core snapshot 2026-05-30 08:01:21 +09:00
manualtesting Initial nexo monorepo migration 2026-05-26 10:42:29 +09:00
store chore(upstream): refresh core snapshot 2026-05-30 08:01:21 +09:00
testlib chore(upstream): refresh core snapshot 2026-05-30 08:01:21 +09:00
utils chore(upstream): refresh core snapshot 2026-05-30 08:01:21 +09:00
web chore(upstream): refresh core snapshot 2026-05-30 08:01:21 +09:00
wsapi chore(upstream): refresh core snapshot 2026-05-30 08:01:21 +09:00
README.md chore(upstream): refresh core snapshot 2026-05-30 08:01:21 +09:00

Server Channels Review Guidelines

When reviewing or writing code in the server channels package, focus on SQL query performance and API layer efficiency.

SQL Store Layer

  • Run EXPLAIN ANALYZE on new or modified queries against a large dataset before merging. A query that performs well on a 12M-post database may degrade significantly at 100M+ posts.
  • Watch for sequential scans on large tables. Ensure appropriate indexes exist for new query patterns.
  • When adding new queries to the store, check whether an existing query already fetches the needed data. Avoid duplicate round trips to the database.

API Layer

  • Minimize database round trips. If an endpoint calls a Get followed by a Delete on the same row, consider using DELETE ... RETURNING to combine them into a single query.
  • Don't add queries that are unnecessary for the operation. The most efficient work is the work you don't do.
  • When adding new API endpoints, add them to the load test tooling so performance can be validated under realistic concurrency.

Permissions and Security

  • Verify that new endpoints enforce appropriate permissions. Rely on the dedicated security review for thorough coverage, but flag anything obviously missing (e.g., an endpoint that skips permission checks entirely).