Scaling React SSR, the future of Styled Components, and making website building fun
An illustrated tour of the triumphs and tragedies experienced while scaling React server-side rendering within a microservice architecture. Learn about isomorphic rendering, load balancing strategies, load shedding with Node Cluster, elastically adding 8x emergency capacity with client-side rendering fallback, the subtle dangers of per-component caching, the importance of keeping your dependencies up to date, the unreasonable effectiveness of the Aggregation of Marginal Gains philosophy, migrating a legacy monolith to use React server-side rendering, and more!
This article is all about the past, present, and future of Styled Components.
In this article Gatsby creator Kyle Matthews walks through the growing complexity of creating web applications and how Gatsby makes website building fun (again!) by creating higher-level components and design tools that allow you to more easily express your intent.
With React 16, instead of unmounting the whole app every time there’s an error, you can use error boundaries. Think of error boundaries like try-catch statements, but for React components.
Learn the React lifecycle methods and when/how to use them.
Treebo is India’s top rated budget hotel chain. They recently shipped a new Progressive Web App as their default mobile experience, initially using React and eventually switching to Preact in production. What they saw compared to their old mobile site was a 70%+ improvement in time to first paint , 31% improvement in time-to-interactive. and loaded in under 4 seconds over 3G for many typical visitors and on their target hardware. This article walks through that change.
Redux Zero is a lightweight state container based on Redux with a single store and no reducers, 100% written in TypeScript. Less than 1kb (gzip). Made for (p)react.
React Sight is a live view of the component hierarchy tree of your React application with support for React Router and Redux.
A deep dive into how Pinterest migrated their web infrastructure to serve React pages, which required moving a huge amount of code without breaking the site. Details on the legacy stack (Django web server and Nunjucks/Jinja template rendering) moving to Node and migrating our templates to React.