Named patterns rarely have anything to do with best practices, even for the hypothetically optimal context the pattern was supposedly invented to handle.

In fact, seeing code that uses a named design pattern is usually a severe bad code smell that people were very confused about how to model the domain problem in an efficient way and fell back to a pattern as a lazy way out.

Using named patterns is the local development equivalent of “nobody got fired for hiring IBM.”