"It may be "simple" today, not as simple tomorrow" - not if tomorrow you make a different class that possibly reuses the simple one internally (perhaps after it was suitably evolved to support that). We often let existing code become bloated too easily by defaulting to adding stuff in. Also, try to design so that renaming the class is not a major undertaking. If it "communicates with a relational database in the most boring, straightforward way imaginable", then it looks like it's a CRUD component, so one option is CrudUserDao.
↧