Welcome to the Treehouse Community
Want to collaborate on code errors? Have bugs you need feedback on? Looking for an extra set of eyes on your latest project? Get support with fellow developers, designers, and programmers of all backgrounds and skill levels here with the Treehouse Community! While you're at it, check out some resources Treehouse students have shared here.
Looking to learn something new?
Treehouse offers a seven day free trial for new students. Get access to thousands of hours of content and join thousands of Treehouse students and alumni in the community today.
Start your free trial![](https://ecs-static.teamtreehouse.com/assets/views/marketing/shared/community-banner-white-47072046c51352fe6a69f5e691ff5700b28bb11d45197d7bdf066d9ea3f72d0c.webp)
![Robert Goddard](https://uploads.teamtreehouse.com/production/profile-photos/131978/micro_rob.jpeg)
Robert Goddard
15,019 PointsWhy not make GifRepository a static class in this case?
Since there is only one method being called on it that seems to be a utility method, why wouldn't that findByName just be a static method and called as a class method (e.g. GifRepository.findByName(...) ) ? I know that the example is showing autowiring, but is there a benefit to instantiating it over just calling it statically?
1 Answer
![Sławomir Lasik](https://secure.gravatar.com/avatar/4030fb6a1cc02a5419bbf24b6f8685af?s=96&d=https%3A%2F%2Fecs-static.teamtreehouse.com%2Fassets%2Fcontent%2Fdefault_avatar-445fbbabfc8dc9188fb5967fe43322ee0c3e0dd1e10f378bf8343784af5a13eb.webp&r=pg)
Sławomir Lasik
7,792 PointsWhen You will consider testing this application You will understand ... ;)