Thought of the day

What drives a service architecture? is it:

  • Fine grained service model alone
  • Or Fine grained service listener model alone driven by a sound EDA,ESB and CEP
  • Or External entities using it?
  • Or Set of assumptions based on business requirements that define service contracts?
  • Or Database/Datasources that are available and what ER model is available for services to use?
  • Or How easy it is assemble services and “orchestrate” them based on business requirements?
  • Or How easy it is for client to invoke these services?
  • Or How services are “shared” on a common namespace (SOAP vs HTTP) debate
  • Or How light weight the I/O or Request/Response model contracts are between clients (with HTTP the general contract becomes redundant with constrained interface)…?
  • Or All of them matter equally? that would ideal but is that practical? I don’t think so …
    • April 7th, 2010 in Java | No Comments
←Older