Finding When Premature Optimization Is Evil

This article is based on the Software Mistakes and Tradeoffs book by Tomasz Lelek and Jon Skeet.

There is an old computer science saying that Premature Optimization is the root of all evil. The saying has stuck around because it’s accurate for a lot of use cases. Without any input data about expected traffic and SLA, it’s hard to reason about your code and its required performance. Optimizing random paths in code in such a situation is like shooting in the dark. You will complicate your code for no good reason. 

Business optimisation architecture – Common architectural elements

In my previous article from this series I introduced a use case around business optimisation for retail stores. 
The process was laid out how I've approached the use case and how portfolio solutions are the base for researching a generic architectural blueprint.
The only thing left to cover was the order in which you'll be led through the blueprint details.

This article starts the real journey at the very top, with a generic architecture from which we'll discuss the common architectural elements one by one.

Blueprints review

As mentioned before, the architectural details covered here are base on real solutions using open source technologies. The example scenario presented here is a generic common blueprint that was uncovered researching those solutions. It's my intent to provide a blueprint that provides guidance and not deep technical details.

Optimize Performance and Render Websites Superfast in ReactJS

To optimize the performance of your React code, you have to make sure that it’s not re-rendering unnecessarily. This is the main reason behind performance bottleneck. Use these tips to improve your codebase and make your website super-fast:

  1. Avoid unnecessary code re-rendering.
  2. Keep your code files short and break them into components.
  3. Use minified production build.
  4. Remove console logs from production code.
  5. For big tables, render a few rows and columns at a time (like FlatList in React Native).
  6. Do not mutate state object.

Let’s discuss all these points, one at a time. Buckle up.