https://medium.com/@march08/architecting-your-react-application-5af9cd65a891

In these days where MVC feels like from the dinosaurs age. Our APIs are serving multiple client apps and a lot of business logic moved to our client applications. Front end development is much more than just nicely coded interface, it’s a lot of programming, sometimes the architecture can be tricky and even serving our web app might not be as straightforward as pushing things via FTP.

So, you or your company has just decided to start a big(commercial, publicly available) project and you’ve decided to use React. You’ve probably already done some research, otherwise you wouldn’t pick React, but there are still a lot of decisions to make what to use in your stack. React is just a view library and there are many missing pieces. State management, routing, localisation, styling and interface, deployment, … Do you need PWA, SSR?