Skip to content
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.

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

Migrate API Server to edge function #73

Open
5 tasks
Mini256 opened this issue Oct 16, 2023 · 0 comments
Open
5 tasks

Migrate API Server to edge function #73

Mini256 opened this issue Oct 16, 2023 · 0 comments

Comments

@Mini256
Copy link
Member

Mini256 commented Oct 16, 2023

This is an exploration task. I'm not sure if this can be completed.

Background

In the past year, more and more applications have begun to use the Severless architecture represented by Next.js + Vercel Serverless / Edge Function.In the initial architecture of the Ossinsight project, we still use "traditional" development and deployment methods:

  • Using Docusaurus as the basic framework for front-end deployment of SSG solutions
  • Develop independent API servers and deploy them into AWS EC2

In the ossinsight-next project, the front-end part has gradually migrated to the SSR architecture of Next.js. In addition, for the following reasons, I think we can start some explorations that migrate the API Server to the Edge Function.

  • Save money, try to remove EC2 machines other than performing background tasks (Import data from GitHub)
  • Improve the delay of the client to the server (mainly when the cache works)
  • TiDB Serverless Driver has been published, direct access to TiDB Serverless in Edge environments is now possible!

Tasks

  • Migrate queries API to Edge function #79
  • Migrate GitHub related API to Edge function
  • Migrate Data Explorer related API to Edge function
  • Migrate Web socket based API to ... (TBD)
  • Migrate light-weight cron job to ... (TBD)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant