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.

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

Jump to bottom

Review API + Storage architecture #10

Open
fivenp opened this issue Nov 14, 2022 · 2 comments
Open

Review API + Storage architecture #10

fivenp opened this issue Nov 14, 2022 · 2 comments
Labels
🏗 architecture

Comments

@fivenp
Copy link
Member

fivenp commented Nov 14, 2022 •
edited
Loading

  • Is it ok to keep Vercel edge functions and CF KV storage?
  • Shall we move away from KV storage?
  • Shall we move away from Vercel edge functions for the API?
  • Shall we move away from Vercel edge deployments for the Frontend?
  • Does the Shield/Badge generator scale enough?
  • Should we consider using helix-flare?
  • Is the logic ok how the Shield/Badge generator triggers a scraper entry?
@fivenp
Copy link
Member Author

fivenp commented Nov 16, 2022

We just got accepted to Cloudflare's D1 alpha.... That means we could use Prisma + D1 for the workers and that would be BY FAR my preferred solution :| 

@dan-lee
Copy link

dan-lee commented Nov 28, 2022 •
edited
Loading

Should we consider using helix-flare?

I would recommend graphql-yoga instead :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
🏗 architecture
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@fivenp @dan-lee