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 to Next? #363

Open
js0mmer opened this issue Oct 14, 2023 · 0 comments
Open

Migrate to Next? #363

js0mmer opened this issue Oct 14, 2023 · 0 comments
Labels
Story Point: 8 introducing a new technology to the stack.

Comments

@js0mmer
Copy link
Member

js0mmer commented Oct 14, 2023

Should we consider migrating to Next?

pros:

  • could help cold starts, response times, SSR
    • bit of an anti-pattern to use express for a lambda function
  • currently http://peterportal.org doesn't work since API gateways only allow TLS. this issue should be avoidable under different infrastructure using Next, there might be other ways to solve this though (if we can put the api gateway behind a cloudfront distribution). (Infrastructure changes #442)

cons:

  • new technology, re-learning required for members
    • additional consideration needed to be taken with client/server components
    • different routing
    • etc.
  • need to look into some other way of handling authentication, sessions (NextAuth?)
    • current setup uses passport/session middleware for Express and it persists between lambda deployments since the session is stored in mongo
@js0mmer js0mmer added the Story Point: 8 introducing a new technology to the stack. label Oct 14, 2023
@js0mmer js0mmer moved this to Tech Debt in PeterPortal Client Oct 14, 2023
@js0mmer js0mmer moved this from Backlog to Tech Debt in PeterPortal Client Feb 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Story Point: 8 introducing a new technology to the stack.
Projects
Status: Tech Debt
Development

No branches or pull requests

1 participant