Hi, my name is
ollieread

In my previous article, I introduced a minimal identity map for Laravel Eloquent. In this follow-up, I'll show you how to better manage the memory usage of the identity map, and prevent memory leaking issues for particularly heavy processes, including Laravel Octane.

Eloquent is a powerful ORM, though it's not without its quirks. One of those quirks is the way it handles model instances, and if you're not careful, you can end up with multiple instances of the same model in memory. This can lead to unexpected behavior and bugs that are hard to track down. In this article, I'll show you how to implement a minimal identity map for Eloquent that will help you avoid these issues.

I've revamped the website with a new design, and a much simpler approach, bringing back my blog which has been missing for too long!

When registering drivers or other types of extensions for Laravel core classes, it's really easy to accidentally eager to load the service and its entire dependency tree! Fortunately, it's almost as easy to avoid it.