What is the better approach? Frontend and backend on zeit now or Frontend on netlify and backedn on zeit now?
up vote
0
down vote
favorite
I have a personal project/ open source project.
https://github.com/drex44/good-food-guide
It is developed in NextJs and until now it was all frontend only. Now to implement better search, I have started creating a backend in nodejs. I will be using Algolia search.
I will change the repo to monorepo so on GitHub, both frontend and backend will be under same repo.
I have confusion over hosting both on zeit now or hosting backend on Zeit now and frontend on netlify.
note: currently, the frontend is on netlify.
architecture devops netlify system-design zeit-now
add a comment |
up vote
0
down vote
favorite
I have a personal project/ open source project.
https://github.com/drex44/good-food-guide
It is developed in NextJs and until now it was all frontend only. Now to implement better search, I have started creating a backend in nodejs. I will be using Algolia search.
I will change the repo to monorepo so on GitHub, both frontend and backend will be under same repo.
I have confusion over hosting both on zeit now or hosting backend on Zeit now and frontend on netlify.
note: currently, the frontend is on netlify.
architecture devops netlify system-design zeit-now
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I have a personal project/ open source project.
https://github.com/drex44/good-food-guide
It is developed in NextJs and until now it was all frontend only. Now to implement better search, I have started creating a backend in nodejs. I will be using Algolia search.
I will change the repo to monorepo so on GitHub, both frontend and backend will be under same repo.
I have confusion over hosting both on zeit now or hosting backend on Zeit now and frontend on netlify.
note: currently, the frontend is on netlify.
architecture devops netlify system-design zeit-now
I have a personal project/ open source project.
https://github.com/drex44/good-food-guide
It is developed in NextJs and until now it was all frontend only. Now to implement better search, I have started creating a backend in nodejs. I will be using Algolia search.
I will change the repo to monorepo so on GitHub, both frontend and backend will be under same repo.
I have confusion over hosting both on zeit now or hosting backend on Zeit now and frontend on netlify.
note: currently, the frontend is on netlify.
architecture devops netlify system-design zeit-now
architecture devops netlify system-design zeit-now
asked yesterday
Dhanraj Acharya
13
13
add a comment |
add a comment |
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53372646%2fwhat-is-the-better-approach-frontend-and-backend-on-zeit-now-or-frontend-on-net%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown