Low query performance with fetched whereIn

English

Draft Disclaimer: Please note that this article is currently in draft form and may undergo revisions before final publication. The content, including information, opinions, and recommendations, is subject to change and may not represent the final version. We appreciate your understanding and patience as we work to refine and improve the quality of this article. Your feedback is valuable in shaping the final release.

Language Mismatch Disclaimer: Please be aware that the language of this article may not match the language settings of your browser or device.
Do you want to read articles in English instead ?

# How whereIn became a growing ballon

  • be wary of where in statements
  • can easily grow to tons of ids
  • less bad when where in is fed a sub query vs fetched query
  • part of common performance issues with syntactic sugar
    • extract to own post
    • array filter map reduce
    • chain of map can be reduce to a single foreach
    • chain of array map and filter can be reduce to just filter
Babacar Cissé DIA
By on

A Solutions Architect and Developer who thrives on crafting digital solutions. Passionate about learning and innovation, he sees challenges as opportunities to build secure, responsive, high-quality applications that drive business growth through cutting-edge technology. His blog serves as a tech memoir, documenting his coding journey and sharing insights into software architecture. It’s a blend of lessons, musings, and tech expertise, providing a glimpse into the art of crafting solutions in an ever-evolving digital landscape.