Introduction When it comes to apps with a lot of data, some SQL queries take more time than expected, especially when we want to search text through several model attributes. This most commonly happens with e-commerce stores, but these kinds of complex queries can happen in social media apps or
Some days ago the React Summit Remote Edition gathered tons of people behind the screen with the promise of putting together popular speakers around the React Community like Kent C. Dodds and Guillermo Rauch among others, but one talk especially caught my attention, React Query: It’s Time to Break up with your “Global State”! by Tanner Linsley. In it,
We usually try to solve performance problems by using #includes to get rid of N + 1 queries but this doesn’t always fix the issue; in fact, it can even create more queries under some circumstances. This post shows a few examples of when that happens and how to deal with it.
Kalil de Lima is a full-stack developer on the Rootstrap team and writes about his experience tackling difficult problems for our many clients. You can also follow Kalil on LinkedIn. Introduction Recently, one of our clients asked us to evaluate the performance of their app in a production environment. To give that
Counter caches are great until you get 20,000 people following the same influencer and the counter cache on that person locks the whole database. The goal of this post is to go through the basics of counter caches explaining possible alternatives to overcome this. What are counter caches for? Counter
