It seems you are referring to the issue more on the conceptual level which is fine but is limited if you don't have exposure toward the real world scenarios, which are many than the above cases. One is that nowadays you can use JAMStack with static site generators like Gatsby and have a web app transition between paradigms, if you would call them so, start as static assets or sites and transition later on into SPA. You can use server side and client side rendering together and combine both benefits.
The trend seen so far is into the JAMStack + SSGs + GraphQL + Apollo etc. Rather than focusing on the this versus this there is another level of application that is much more efficient and effective.
Thanks, appreciate your views! Yep, I was talking on the conceptual level, I know a lot of other permutations and combinations are possible too, especially these days.
JAMStack is good but you still need something on server side to handle the GET/POST/PUT requests, right? Its immaterial whether I use Gatsby, Jekyll, Pelican or even create a custom one for my own app, the fact that whether or not the front-end is separated from back-end (which rules out server side templates using twig, jinja, etc.) is the main discussion point at the conceptual level.
I know about all these trends, except SSG. Never heard of that, are you referring to SSG Solutions Pvt. Ltd.?
It seems you are referring to the issue more on the conceptual level which is fine but is limited if you don't have exposure toward the real world scenarios, which are many than the above cases. One is that nowadays you can use JAMStack with static site generators like Gatsby and have a web app transition between paradigms, if you would call them so, start as static assets or sites and transition later on into SPA. You can use server side and client side rendering together and combine both benefits.
The trend seen so far is into the JAMStack + SSGs + GraphQL + Apollo etc. Rather than focusing on the this versus this there is another level of application that is much more efficient and effective.
Thanks, appreciate your views! Yep, I was talking on the conceptual level, I know a lot of other permutations and combinations are possible too, especially these days.
JAMStack is good but you still need something on server side to handle the GET/POST/PUT requests, right? Its immaterial whether I use Gatsby, Jekyll, Pelican or even create a custom one for my own app, the fact that whether or not the front-end is separated from back-end (which rules out server side templates using twig, jinja, etc.) is the main discussion point at the conceptual level.
I know about all these trends, except SSG. Never heard of that, are you referring to SSG Solutions Pvt. Ltd.?
You use graphQL which is far better than rest api. SSG is static site generators.