Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 5 years ago.
Improve this question
I keep seeing references to JAMstack web development architecture.
From the web page Jamstack.org it is not obvious how JAMstack is different from the common JavaScript SPA frontend with REST API backend architecture.
What is the key difference?
Javascript Heavy front end - APIs for everything else - templated Markup
jamstack.org is the canonical site with examples and explanation
The key thing that differentiates JAMstack from other architectures is the middle part. APIs for every back end function means that backend can be spread out/scaled with ease.
EDIT: I should add that the term was coined by a CDN company Netlify which stands to benefit from a wider adoption of the architecture.
Related
Closed. This question needs details or clarity. It is not currently accepting answers.
Want to improve this question? Add details and clarify the problem by editing this post.
Closed 9 months ago.
The community reviewed whether to reopen this question 9 months ago and left it closed:
Original close reason(s) were not resolved
Improve this question
In nextjs u can write API routes using the api named directory inside the pages directory, thus i was wondering if i can write all of my server code(api endpoint,database queries...ect) inside of NextJS instead of having an actual nodejs app running elsewhere?
The short answer: Yes. Nextjs is in fact an Nodejs app itself.
The long answer:
Depending on your apps usage and scale and the size of your team there are some nuances to consider.
If you use Nextjs for both Server-side Rendering (SSR) and handling api calls, it will effectively have two responsibilities.
This is perfect for small teams because the stack is relatively uncomplicated and all in the same repository (and module).
At a certain scale you might want to optimise deployments to gear towards either rendering or handling api calls. It might become difficult to keep both extremely highly performing - at which point a separate, specialised, backend might become relevant.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 5 years ago.
Improve this question
I am building a large web application in node.js and I'm always faced with the question 'where should the heavy lifting be done?' I was always taught that the 'logic' should always be done in the backend of the application, but with modern computers and browsers being so powerful it begs the question if some of the heavy lifting logic can go in the front end.
So context to my specific application. Using angularjs and postgres. A specific question is: would it be a bad practice to have the back end api fetch the rows from the database and pass it to the front end. And then have the front end deal with the logic of deriving the information from the rows? Things like counts with in date ranges and such. (ignore security for this question) or should all the be done on the backend?
If it deals with script that doesn't need to be hidden or is not a secret, then I would suggest putting most of it on the front-end, it would lessen the stress on your server and give you more space to run more processes at a time without filling the ram.
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 6 years ago.
Improve this question
Guys i'm new in Nodejs,
please can it be used on the web like php?
First you decide what type of situation you have.
If you want to make shopping site, social network etc which use large data processing , then you go for node.js (for example linkedin is made in node.js ).
But if your website does not require much data processing in server side you can go for php.
Nodejs is little difficult to use but once you use it perfectly your website will run smooth.
Both are good languages.
Yes you can easily use nodejs as a server side language.
Nodejs is faster than php. You can use nodejs to speedup your loading speed of your website.
Because nodejs heavily use callbacks.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 10 months ago.
Improve this question
When it comes to these principles like architecture and Infrastructure how would you describe them? The actual meaning and in development where its used. So for example is it like infrastructure is the actual website and architecture is the plans or so called blue prints (UML) in the background?
Infrastructure is a word used for the underlying components that support the operation of something. In your example, you said a "web site" - so things like load balancers, web servers, database servers, and the operating systems that run those servers would be included in the infrastructure. This can go more granular, to include the details of the data centers that the servers operate in. [power generators, cooling, etc.]
You are correct in that architecture is use to speak of the "blue prints", or the design of something. UML, which you mentioned, is one way to express and visualize a design. It tries to answer questions like: What are the components? What are the relationships between the components? What do they do, and not do?
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 8 years ago.
Improve this question
One of the main features in my website is a simple One-to-One chat.
I'm debating whether or not I shall dedicate a server (or a cluster) for the sole purpose of this chat feature. The simpler option would be combining this feature as part of the web-servers and just scale out when necessary.
It is worth mentioning I'd like in the future to enable images transfer within the chat.
So what is the better option and why?
Well yes, Whether to use another dedicated server is not depending on how much traffic your site will have to handle. If you're dealing with images It will be a good idea to store them in another server and keep the root server clean.