title: naming standards/conventions and what should a 'Service' class should do
body: <p>What would you name a class which does only a very small part of functionality, for example taking a recurring payment profile and marking it as 'failed'.</p>
  
  <p>Is it correct to name it <code>RecurringPaymentProfileMarkAsFailedService</code>? I know it's just a name, but I would like to adher to standards / convention.  Is this what a 'Service' class should do, or is this a different design pattern?  I am trying to follow up on the line of the SRP principle, and thus if I am correct one would end up with a lot of small classes, each specialised in one task.  I would like to define a correct naming standard.</p>