docs: add Java migration plan for Vercel cost optimization#265
docs: add Java migration plan for Vercel cost optimization#265longsizhuo wants to merge 1 commit intomainfrom
Conversation
Created a detailed MIGRATION_PLAN.md documenting how to migrate high-frequency and long-running APIs (like analytics and AI chat) to an independent Java backend to reduce Vercel serverless usage. Co-authored-by: longsizhuo <114939201+longsizhuo@users.noreply.github.com>
|
👋 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 New to Jules? Learn more at jules.google/docs. For security, I will only act on instructions from the user who triggered this task. |
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This PR introduces a comprehensive
MIGRATION_PLAN.mddocument.Based on the provided Vercel usage data (high Function Invocations, Edge Requests, ISR Operations, and excessive Fluid Active CPU), the plan analyzes current API endpoints and outlines a phased strategy to migrate the most resource-intensive Next.js App Router API routes (
/api/chat,/api/analytics,/api/suggestions, and/api/upload) to an independent Java Spring Boot backend.This approach acts as a BFF (Backend For Frontend) to drastically reduce Vercel Serverless computing costs while retaining the benefits of Next.js and Fumadocs for the UI. Mermaid flowcharts are included for visualizing the before-and-after architecture.
PR created automatically by Jules for task 2575053149918218439 started by @longsizhuo