⚡ Bolt: Prevent query waterfall in articles API

[mkk2026]

💡 What:
Refactored the GET handler in src/app/api/articles/route.ts to execute db.securityArticle.findMany, getStats(), and db.securityArticle.count concurrently using Promise.all.

🎯 Why:
Previously, these three independent operations were awaited sequentially, creating an unnecessary query waterfall. Parallelizing them reduces the overall latency of the endpoint.

📊 Impact:
Reduces database round-trip times and overall request latency for the articles endpoint by overlapping the execution time of the list fetch, the total row count, and the cached stats retrieval.

🔬 Measurement:
Use network profiling tools to measure the TTFB (Time to First Byte) of the /api/articles endpoint. It should reflect a noticeable reduction in latency under load.

---

PR created automatically by Jules for task 5528215498305987729 started by @corebrimtech

Summary by CodeRabbit

• Performance
  • Improved article listing responses by loading articles, summary stats, and total counts in parallel, which should reduce wait times.
  • Pagination now uses a precomputed total, helping keep results more responsive under load.

[google-labs-jules]

👋 Jules, reporting for duty! I'm here to lend a hand with this pull request.

When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down.

I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job!

For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with @jules. You can find this option in the Pull Request section of your global Jules UI settings. You can always switch back!

New to Jules? Learn more at jules.google/docs.

---

For security, I will only act on instructions from the user who triggered this task.

[chatgpt-codex-connector]

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.

[coderabbitai]

📝 Walkthrough

Walkthrough

The GET /api/articles handler was refactored to fetch the article list, cached dashboard stats, and total count concurrently using Promise.all, replacing sequential awaits. The JSON response now uses the precomputed total for pagination instead of a separate count query.

Changes

Concurrent data fetching in articles API

Layer / File(s)	Summary
Parallelize queries and update response src/app/api/articles/route.ts	Article data, cached stats, and total count are fetched concurrently via Promise.all, and the response uses the precomputed total for pagination.total.

Estimated code review effort: 1 (Trivial) | ~5 minutes

Poem

Three queries once hopped in a row,
Now together they leap and go!
Promise.all bundles them tight,
Faster results, pure delight,
This bunny thumps approval below. 🐇

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly summarizes the main change: parallelizing the articles API queries to avoid a waterfall.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches

📝 Generate docstrings

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch bolt/api-waterfall-optimization-5528215498305987729

Warning

There were issues while running some tools. Please review the errors and either fix the tool's configuration or disable the tool if it's a critical failure.

🔧 ESLint

If the error stems from missing dependencies, add them to the package.json file. For unrecoverable errors (e.g., due to private dependencies), disable the tool in the CodeRabbit configuration.

src/app/api/articles/route.ts

ESLint skipped: missing config or dependency (missing-dependency). The ESLint configuration references a package that is not available in the sandbox.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[coderabbitai]

🧹 Nitpick comments (1)

src/app/api/articles/route.ts (1)

65-99: 🧹 Nitpick | 🔵 Trivial

Consider connection-pool impact under load.

Running three DB-bound operations concurrently per request triples momentary connection usage compared to the sequential version. Worth monitoring Prisma pool saturation (connection_limit) under peak traffic, especially since getStats() itself issues 4 parallel counts when the cache is cold.

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@src/app/api/articles/route.ts` around lines 65 - 99, The concurrent
Promise.all in the articles route is increasing Prisma connection usage per
request, especially because getStats() can fan out into multiple counts when
cold. Update the query flow in the articles route handler to avoid running all
DB-bound work at once; either sequence the count/stats calls or otherwise limit
concurrency, and keep the logic centered around getStats,
db.securityArticle.findMany, and db.securityArticle.count.

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Nitpick comments:
In `@src/app/api/articles/route.ts`:
- Around line 65-99: The concurrent Promise.all in the articles route is
increasing Prisma connection usage per request, especially because getStats()
can fan out into multiple counts when cold. Update the query flow in the
articles route handler to avoid running all DB-bound work at once; either
sequence the count/stats calls or otherwise limit concurrency, and keep the
logic centered around getStats, db.securityArticle.findMany, and
db.securityArticle.count.

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: bc00ddd5-a4d2-4228-83d8-24b49662f857

📥 Commits

Reviewing files that changed from the base of the PR and between 558fb10 and dad5730.

📒 Files selected for processing (1)

• src/app/api/articles/route.ts