William Vambenepe's blog

IT management in a changing IT world

At present, nearly all strains are resistant to penicillin, and many are best online price viagra to nafcillin, leaving only a narrow selection of drugs such as vancomycin useful for treatment.In the Republic of Georgia, the Eliava Institute of Bacteriophage, drug generic viagraThese developments show promise as a means to free viagra order online the growing bacterial resistance to existing antibiotics.Recent research on the molecular biology and genomics of non prescription viagra has focused on the interaction with the immune system, anti-cancer potential, and potential as a biotherapeutic agent in cases of antibiotic-associated diarrhoea, travellers' diarrhoea, pediatric diarrhoea, inflammatory bowel disease and irritable bowel syndrome.Unlike previous treatments for infections, which often free sample prescription for viagra of administering chemical compounds such as strychnine and arsenic, with high toxicity also against mammals, antibiotics from microbes had no or few side effects and high effective target activity.

17
Nov
2005

Humble Architecture

by William (@vambenepe on Twitter)

In many respects, the principles of Service-Oriented Architecture (SOA) can be summarized as “be humble”. “Service” comes from “servus”, Latin for “slave”. It doesn’t get any more humble.

More practically, this means that the key things to keep in mind when creating a service, is that you are not at the center of the universe, that you don’t know who is going to consume your service, that you don’t know what they are going to do with it, that you are not necessarily the one who can make the best use of the information you have access to and that you should be willing to share it with others openly (instead of the all-too familiar syndrome where everyone wants to consume other people’s services but no-one see the need to expose themselves as services because they think they “own” the connection to the human or they “own” the business process). You also shouldn’t assume that some human needs to come to you and ask for permission to use your service but instead you should provide machine-readable descriptions of it as well as quality documentation. And don’t assume that everyone speaks the same language you speak. In case of doubt in designing a service-oriented system, ask yourself “what would a slave do?”.

Focused, standard-based services are humble. Portlets are humble. RSS feeds are humble. Giant software suites and all-encompassing frameworks are not humble.

Successful open source projects are humble almost by definition. Large software companies rarely have humility genes in their DNA, unless it’s been beaten into them by customers.

Related posts:

  1. David Linthicum on SaaS, enterprise architecture and management
AddThis Social Bookmark Button Follow @vambenepe on Twitter.

This entry was posted on Thursday, November 17th, 2005 at 6:29 pm and is filed under Everything, Tech. You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site.

«
»

2 Responses to “Humble Architecture”

  1. William Vambenepe — REST in practice for IT and Cloud management (part 3: wrap-up) Says:
    December 10th, 2009 at 2:16 am

    [...] a vibe behind REST design. You can copy the technology and still miss it. I described it in 2005 as Humble Architecture, and applied to SOA at the time. But it describes REST just as [...]

  2. William Vambenepe — Taxonomy of Cloud Computing Benefits Says:
    January 11th, 2010 at 11:34 am

    [...] right. It’s been discussed, manifesto’ed, buried and lampooned many times before (this was my humble take on it). Whether it’s because of WS-* or, more likely, java2wsdl we have [...]

Leave a Reply