EDABlog

From Richard Turners blog

SO and OO are complementary technologies:

• SO is how one thinks about building systems as a whole:
  • A System is a set of deployed services cooperating in a given task
    • Systems are built to change
    • Systems adapt to the introduction of new services after deployment.
  • A service is a program you interact with via message exchanges.
    • Services are built to last
    • Availability and stability are critical and the responsibility of the Service Owner.
    • Services are fractals – one service can contain other services, which can contain other services,  …
• OO is important WITHIN the service boundary
• OO technologies and approaches are used to build a service physically
• OO technologies store and retrieve data to/from internal data stores, perform calculations or business functionality, etc.
• This is “business as usual” for most developers 
  

OO is good at reducing, managing and modeling complexity however it is quite likely that many services will result in anemic domain model in which case OO looses most of its benefits. For these smaller services they will look Procedural regardless of the technique used.