Andrey (azangru) wrote,

I am having these discussions daily at work. Our main web application is a React/Redux app that uses server-side rendering for SEO and social-media sharing purposes. The temptation of having one and the same codebase both on the server and on the client was very powerful. The beauty of having the code modularized into clearly defined components was also an attraction. And I am still not convinced that it is necessarily a bad architectural decision. But the sad reality is that our app is bulky and yes, suffers from the symptoms he is describing.

There are lots of web sites that have followed the hype and by now have a similar architecture. The New York Times is famously re-architecting their site using server-side-rendered React and GraphQL. The Wall Street Journal, The Economist, The Intercept, Vice, and Wired also have React with server-side rendering. Pinterest shared quite exitedly how they moved from a Django monolith to a dedicated service with universal React. This is still what the cool kids want to do. But there might be signs that the tide is turning, and that either this will be replaced by a more nuanced approach, or people will start losing trust in apps that share their client-side and server-side code and go back to writing server-side templates with sprinkles of client-side javascript for adding interactivity.

And meanwhile, our company lacks manpower and will power to re-write our web app in a more performant manner.

  • (C)opied from Twitter

  • (no subject)

    OMG, a Russian clone of MasterClass! The original for comparison:

  • (no subject)

    Sanjay Gupta on Joe Rogan: yes, I agree, they shouldn't have said horse dewormer; no, I don't know why they did; no, they shouldn't have done that;…

  • Post a new comment


    default userpic
    When you submit the form an invisible reCAPTCHA check will be performed.
    You must follow the Privacy Policy and Google Terms of use.