Data Fetching in React.js – DEV Community

When you have been utilizing React.js you have to be conversant in Consumer Facet Rendering(CSR). To clarify it briefly, CSR is when the Web site is constructed and assembled on the Consumer Facet. So the complete App is loaded and rendered within the Consumer Facet which is the browser. Information fetching takes place within the browser itself. Since React solely helps CSR, it has some limitations. Right here comes Subsequent.js.

Subsequent.js is a React Framework for creating Server Facet Rendered Apps.

Subsequent.js offers 4 alternative ways to Fetch knowledge.

  1. Information Fetching throughout construct time – Static Web site Era (SSG)
  2. Information Fetching throughout request time – Server Facet Rendering (SSR)
  3. Information Fetching based mostly on situation – Incremental Web site Regeneration (ISR)
  4. Information Fetching on Consumer facet – Consumer Facet Rendering (CSR).

Earlier than we begin I’ve already created a Demo of knowledge fetching in Subsequent.js. You’ll be able to verify it right here

Static Web site Era (SSG):

That is additionally known as as Construct time knowledge fetching. Right here we fetch the information on the Construct time of the location and add it to the web page. Therefore we get a web page which is already loaded with knowledge. For performing construct time knowledge fetching we use getStaticProps() technique. Throughout the construct strategy of the web site, the information is fetched by the getStaticProps() technique and handed onto the web page. Utilizing this knowledge the web page is totally constructed after which served statically. The web page is not going to be construct once more till a brand new construct is triggered. So the information gained’t be refreshed and up to date. getStaticProps()runs at construct time solely. The tip end result here’s a static web site generated at construct time which is able to be served.

Code Instance:

//Export this perform beneath your web page which you wish to render statically
export async perform getStaticProps(context) {
  //Make API name right here 
    const res = await fetch(`your API url`);
    const knowledge = await res.json();
  return {
    props: { knowledge }, // will likely be handed to the web page part as props
Enter fullscreen mode

Exit fullscreen mode


  1. Quick load time for the reason that web page is already generated.
  2. Higher website positioning for the reason that contents of web page is on the market even earlier than the consumer requests.
  3. Can be utilized for Static Facet Era.

When to Use?

  1. Whenever you need the information to be prepared earlier than the consumer requests it.
  2. When the content material isn’t going to vary.
  3. When website positioning and Efficiency is the highest most precedence for that web page.
  4. When the information is on the market at Construct Time.

Use Case:

Think about you’re constructing a portfolio web site that renders markdown blogs at construct time. In such case you need to use getStaticProps() to learn the blogs and create a Weblog web page on construct time. So subsequent time once you add a brand new weblog, the web site is constructed once more and new blogs are proven.

You’ll be able to mix getStaticProps with getStaticPaths to create pages for dynamics routes. For instance. Let’s imagine you have got a weblog web page on URL “” which lists down all of the blogs and a particular weblog web page “” which is a dynamic route which reveals a particular weblog. In such case you need to use these two capabilities to create all of the dynamic paths at construct time, create pages for it utilizing getStaticPaths and fill it with content material utilizing getStaticProps . All this on construct time. So ultimately what you have got is an internet site with a number of Static pages corresponding to every particular person weblog. My private portfolio makes use of this method.

Refer this demo for understanding about Static Props and Static Paths.

Server Facet Rendering (SSR):

Use getServerSideProps() to fetch knowledge on Server on every consumer request. This perform fetches knowledge on each consumer request on the server. A consumer requests a web page, the server finds a web page for that URL, builds it by fetching knowledge and returns again the web page. For the reason that web page makes use of server facet rendering, the information is fetched on the server and knowledge is handed as props to the web page .Web page accepts the props and is constructed on the server after which returned again. So for each new request, web page is constructed once more. Since a totally assembled web page is returned the customers can straight begin interacting with it. getServerSideProps()runs on every request on the server facet solely.

Instance code:

//Export this perform beneath your web page which you wish to render on server
export async perform getServerSideProps(context) {
  //make your API request right here
    const res = await fetch(`your API Url`)
  const knowledge = await res.json()

  return {
    props: {}, // will likely be handed to the web page part as props
Enter fullscreen mode

Exit fullscreen mode


  1. The web page is on the market for consumer interplay immediately.
  2. The web page stays up to date as a result of the web page is constructed on each request.
  3. Nice for website positioning.

When to make use of:

  1. Whenever you want to present a web page which has knowledge that’s up to date incessantly.
  2. Whenever you need the information to be obtainable to consumer as quickly because the web page hundreds.

Use Case:

Let’s imagine you’re making a E Commerce web site. On Purchasing web page the content material will get up to date on daily basis based mostly on stock. Therefore you may use Server Facet Fetching Technique which builds the web page each time a consumer requests it. The consumer will likely be served with a web page with the freshest content material.

Incremental Web site Regeneration:

This can be a mixture of Server Facet Rendering and Static Web site Era. Right here the information is served statically however based mostly on a sure situation or time the pages are rebuilt. This method means that you can create up to date static pages after you have got constructed your web site.

To make use of Incremental Web site Regeneration add a revalidate prop to getStaticProps() technique .

Instance Code:

export async perform getStaticProps(context) {
//make API calls right here
  const { knowledge } = await fetch(`Your url`);
  return {
    props: { knowledge }, // will likely be handed to the web page part as props
        revalidate:30 //The web page will likely be constructed once more in 30seconds
Enter fullscreen mode

Exit fullscreen mode

The static web page is constructed on Construct time and served to the consumer when the consumer requests. When the consumer once more requests the web page after 30 seconds, Subsequent.js begins rebuilding the web page once more. So after rebuilding the up to date web page is proven to the consumer. The outdated web page nonetheless stays within the cache. If a consumer requests the web page once more earlier than the 30 seconds window, the identical outdated web page is proven.


  1. You’ll be able to use SSG and SSR collectively.
  2. Nice for website positioning and Efficiency.

When to make use of:

  1. Whenever you need pace of Static web site but in addition want to present up to date knowledge infrequently.
  2. When the information is up to date however not typically.

Use Case:

ISR can be utilized once you wish to scale up a static web site. On this case you don’t must construct the static web site when a brand new replace is made. You’ll be able to cross in a revalidate prop and the web page will rebuild itself. It will enable you to in scaling your Static websites.

Consumer Facet knowledge fetching

That is the method what a plain React app makes use of. On this method we fetch the information on the Consumer facet of the applying. For the reason that web page is assembled on the consumer facet we name this method as Consumer Facet Rendering. To deal with CSR in subsequent.js we use useEffect() hook. The useEffect() hook runs when the part hundreds. You’ll be able to add your knowledge fetching strategies in useEffect() hook to carry out knowledge fetching on Consumer Facet.

Instance Code

const [users,setUsers] = useState(null)

    const fetchData=async()=>{
        attempt {
            const { knowledge } = await axios.get(
        } catch (error) {


Enter fullscreen mode

Exit fullscreen mode


  1. The web page gathers knowledge on the consumer therefore there’s much less load on the server.
  2. The web page will all the time serve newest knowledge.
  3. Nice for consumer interactivity.

When to make use of:

  1. When your web page has knowledge which is up to date very incessantly(each minute).
  2. The place consumer interplay with the information is extra.

Use Case:

Dashboard constructed with React/Subsequent.js use this method. You’ll be able to create a Dashboard web page and as soon as the web page is assembled you may make a request for the information utilizing the useEffect() hook. You’ll be able to add a threshold to set the web page refresh. Therefore when the edge is handed the web page refreshes and new knowledge is fetched.


We now have now learnt 4 methods of fetching knowledge in Subsequent.js. All of the methods fully totally different from one another and have their very own execs and cons. And you recognize the perfect factor about Subsequent.js??

You don’t have to decide on one to your venture! You’ll be able to choose a technique for one web page and different for one more web page. You’ll be able to select the way in which you want to fetch knowledge on the necessity of that web page. So in your subsequent Lodge reserving web site you possibly can have your house web page generated Statically when you can generate your Listings web page dynamically on Server!

Thanks for studying. I hope you learnt one thing new at this time. If you happen to nonetheless have any downside be at liberty to message me on my twitter.

Add a Comment

Your email address will not be published. Required fields are marked *