In the enterprise space, a considerable amount of innovation is happening in two dimensions: on the edges of the enterprise and in the spaces between enterprises. On the edges, we see energy being spent in frameworks that live above middleware (domain-independent ones, such as Ajax, as well as domain-specific ones, aligned around specific industries) and those that work in conjunction with devices [classical mobile devices and devices with Radio Frequency Identification (RFID) tags]. In the spaces between, we see the formation of systems of systems (both legacy and new systems).

In the context of such Web-centric systems, services have proven to be an essential mechanism in both dimensions. On the edges, services deliver behavior in a manner that transcends the underlying technology. In the spaces, services provide a powerful means of semantically rich communication between systems of various kinds.

That being said, services are an important but insufficient mechanism for the construction of systems. This statement is a gross simplification, but in general, services are less well-suited for high-frequency or very small-grained connections. Furthermore, services are certainly not the only mechanism of decomposition suitable for the architecture of individual systems.


Surrupiado do blog do cara.

So? Booch é Booch. Há pouco lembrei que ele é, na minha opinião, o ARQUITETO. Mas ainda não concordo que Serviços (em uma SOA) não sejam 'adequados' para conexões de 'alta frequência' ou de pequena granularidade. Serviços básicos são (ou deveriam ser) pequenininhos. Todos devem ser 'assíncronos', único fato que pode impedir sua adequação a conexões de 'alta frequência'? Sigo na dúvida..