IT:AD:Patterns:Service Pattern


In an app, it's surprising how little actually needs state. I know that sounds weird at first…

Consider how many static methods, helper methods we have in most apps.

Stuff like: DbHelper, AppSettingsHelper, ConfigHelper, EnvironmentHelper. These should all be stateless.

It turns out that a stateless class of methods all focused on the same functionality has another word for it: a Service.

Once that is understood, instead of a whole bunch of ad-hoc static (and unfortunately some times non-static) helper classes, an app quickly gains an organised set of Services.


And funnily enough, that' much of what XActLib focuses on providing (in a modular, maintainable way of course).