How to apply Single Responsibility Principle to a service class
- by Shekhar
Hello
Suppose we are designing a UserServiceImpl class which does CRUD(Create, Read, Update, and
Delete) operations. In my view Create, Read, Update, and Delete are four reasons for a
class to change. Does this class violates Single Responsibility Principle? If it violates,
then should we have four classes like CreateUserServiceImpl, ReadUserServiceImpl,
UpdateUserServiceImpl, and DeleteUserServiceImpl. Isn't it an overkill to have lots of
classes?
Thanks
Shekhar
