Post #2523161

Working on optimizing a route where the first instinct was concurrency but it blows up and a deeper inspection finds hundreds of repeated queries. The fun part is using the repository pattern here has led to a legacy code issue where the slice doesn't line up with what the business logic needed and without rewriting an entire layer 😱 the only option is drilling the results of shared queries down N-layers of functions or finding some way of caching these queries that can be shared.