Skip to content

Migrate to Next? #363

@js0mmer

Description

@js0mmer

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    Story Point: 8introducing a new technology to the stack.

    Type

    No type

    Projects

    Status

    Done

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions