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

Rethink architecture #164

Open
H1ghBre4k3r opened this issue Aug 12, 2022 · 0 comments
Open

Rethink architecture #164

H1ghBre4k3r opened this issue Aug 12, 2022 · 0 comments
Assignees
@H1ghBre4k3r
Labels
question Further information is requested

Comments

@H1ghBre4k3r
Copy link
Member

Currently, we are relying entirely on NestJS. I am not entirely sure, if this is a good idea...
We could think about adopting T3, since we would be able to create a uniform, typesafe API with support for both, web and mobile.

Next.js offers great features for designing APIs, featuring SSR and SSG. Next-Auth provides "native" authentication for several auth providers, which would allow us to remove the current (kinda hacky) solution. Furthermore, a typesafe API with tRPC would reduce the risk of regression/implementation errors.

We could also think about "plugging" together our own system consisting of Next.js, NextAuth and tRPC (without the need of Tailwind, which is currently included in T3).

On the other hand, we could switch to a complete BaaS, e.g., nHost, AppWrite or Supabase.
@H1ghBre4k3r H1ghBre4k3r added the question Further information is requested label Aug 12, 2022
@H1ghBre4k3r H1ghBre4k3r self-assigned this Aug 12, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@H1ghBre4k3r H1ghBre4k3r

Labels
question Further information is requested
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@H1ghBre4k3r