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

Where does next.js go in the stack? Middle-end? #849

Closed
FrancosLab opened this issue Jan 21, 2017 · 2 comments
Closed

Where does next.js go in the stack? Middle-end? #849

FrancosLab opened this issue Jan 21, 2017 · 2 comments

Comments

@FrancosLab
Copy link

Although I feel confident that Next is more-or so the middle-end of an application.
Sometimes I find myself hypothetically questioning if Next is right for the job for hypothetical projects.

Let's say for whatever reason platform like facebook was to be rewritten, would Next be suited for handling that and where would it go in the stack?

@arunoda
Copy link
Contributor

arunoda commented Jan 21, 2017

It's definitely for the front end with BYOB(Bring Your Own Backend)

Although it's possible to do some backend work in Next.js, you should only do it to support the UI. Not to serve data.

@rauchg
Copy link
Member

rauchg commented Jan 21, 2017

You could definitely attach arbitrary routes to your next server (examples: https://github.com/zeit/next.js#custom-server-and-routing), but we don't recommend it.

It's much better suited to plugging into other backends and APIs. For example, you can host your microservices on https://now.sh and query them to get your data (see the examples in the README using fetch).

Thanks for your question!

@rauchg rauchg closed this as completed Jan 21, 2017
@lock lock bot locked as resolved and limited conversation to collaborators May 12, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants