Skip to content

docs: Update logic placement guidelines in API architecture #17234

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
szokeasaurusrex wants to merge 2 commits into
base: master
Choose a base branch
from
+2 −2
Open

docs: Update logic placement guidelines in API architecture #17234

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
f136d32
docs: Update logic placement guidelines in API architecture
szokeasaurusrex Apr 2, 2026
fd67053
remove unrelated change
szokeasaurusrex Apr 2, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions develop-docs/sdk/getting-started/standards/api-architecture.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -26,10 +26,10 @@ When deciding where new logic should live, default to server-side (Relay). Proce

Put logic in the SDK only when it genuinely needs to run client-side:

- It **MUST** run before data leaves the customer's application (e.g., user-controlled filtering like `before_send_*`)
- It needs to run before data leaves the customer's application (e.g., user-controlled filtering like `before_send_*`)
- It requires access to platform-specific APIs
- It's strictly latency-sensitive
- It **MUST** function in offline scenarios
- It needs to function in offline scenarios

If data has already been collected, transform it in Relay.

Expand Down
Loading