search

Melkeydev / astrostation

https://astrostation.me
MIT License
200 stars 42 forks source link

Migrate to NextJS? #265

Closed Hacksore closed 1 year ago

Hacksore commented 1 year ago

Benefits:

Drawbacks

Melkeydev commented 1 year ago

The drawbacks

Melkeydev commented 1 year ago

On a serious note - @royanger and I have been SLOWLY talking about making a BE for this.

royanger commented 1 year ago

I don't think we need Next. We aren't going to use page based routing, SSR or SSG, etc, e tc. The only benefit is the API route/serverless, but if we want to build the backup with serverless we can handle that other ways.

Hacksore commented 1 year ago

I don't think we need Next. We aren't going to use page based routing, SSR or SSG, etc, e tc. The only benefit is the API route/serverless, but if we want to build the backup with serverless we can handle that other ways.

🧢.

Your best bet is to use next for the freemium tier.

Trying to roll your own backend is going to have cost and scaling problems.

If you have a compelling reason to build a fully custom solution so be it but personally I find next to be the most low effort & cost effective solution.

royanger commented 1 year ago

There are definitely some free options out there. I believe that Melkey is already paying on Vercel, but that's not really an issue either way. We don't need Next to use serverless on Vercel if we want to use serverless on Vercel. We can add serverless to any framework, and the Vercel CLI can even provide a dev server for a nice DX.

Hacksore commented 1 year ago

Closed in favor of https://github.com/MelkeyOSS/astrostation/issues/238, the vercel serverless looks like a good option for API routes.

However, there is still an issue of requiring a database but I'll let the tech leads figure that one out (i just work here).