Recently, client-side rendering seems to have overshadowed server-side rendering. But, there are a lot of pros and cons to consider when deciding how to structure your next project. In this post, we’re going to talk about traditional server-side rendering, and answer the following questions:
- What is server-side rendering?
- What is server-side rendering good for and why?
- How does it differ from client-side rendering?
Let’s get started!
So…what is server-side rendering?
It’s one way to send data to a user’s browser in order to display content. The content itself is converted to HTML in the server, rendered, and then sent to the browser. …
A quick overview to get you started
Grabbing data from an API endpoint can be simple if you only need a couple of bits from it. But it can get complex quickly, so if you want to try and organize things, GraphQL might be something you’ve started looking into.
The Problems with traditional REST APIs
JSONPlaceholder is an API where you can fetch fake data. From their /users endpoint, you can simply grab the name of a user and their email. What about when you find a more complex API, and need more than just a couple of values? …
About
