3 ms·
Fetching and collating data from multiple other APIs, then creating server-rendered HTML responses to the browser. Most of the Javascript was not for interacti
by bovermyer 4y ago
Fetching and collating data from multiple other APIs, then creating server-rendered HTML responses to the browser.
Most of the Javascript was not for interaction, but for serving ads, really.
- blueslurpee 4y agoInterestingly enough, assuming you use React this is how I see the role of something like Remix[0], which serves as a "rendering layer" that aggregates application data from different API's/stores and then sends a cachable HTML representation to the client which is thereafter hydrated. It's not quite a backend and it's not quite a frontend, but it sort of sits in the middle and (hopefully) helps you achieve lower latency. I haven't used it myself but I think it's a promising idea and based on your post I gather a similar concept worked very well for you. 0: https://remix.run/ https://remix.run/