This post suggesting a need for extreme standardisation needs to be discussed within industry. The idea of having extreme standardisation is extremely appealing but highly impractical. Pulls and counter-pulls within industry will make sure that there are always competing standards.
Vendors dont agree on Who decides on standardisation. There are multiple competing bodies even in standard setting space. Who decides what are the categories for standards? Should everything be in standard. That would imply commoditisation. What will vendors bring in as differentiation? There are no easy answers. If we ignore these questions then we will end up with surfeit of standards on top of existing mess.
As they said in vedic period "pinde pinde matirbhinna". Translated in English it means, every soul has different thinking. Implied in that is the notion that no thinking is superior or inferior, so who is to say which one should become standard? Each different specification mechanism or execution methodology is mostly in response to something desired by user community. So in some sense they represent user's aspirations (and vendor's motivations). How can these different motivations and aspirations be reconciled?
So what is the way out? Well there are ways of tackling these tricky questions.
For example instead of relying on extreme standardisation, industry bodies can work on interoperability standards. To do that, first thing as an industry we must agree on means to define categorisation and 'Domains of discourse'. We can then go on to develop interoperability standards for these various domains (intra domain as well as inter domain). Within IT there are various domains of discourse, for example if you consider IT change management category, the domains could be business strategy, IT strategy, portfolio planning, requirement & scoping, design & build, verification & validation, roll out & operational management, systems retirement etc. Similarly for different categorisation there will be different domains of discourse. Each of these domains will have many competing specification mechanisms and execution methodologies. What we need is means to interoperate between these specifications and methodologies for a domain of discourse and across domain of discourse.
With such interoperability standards in place the deliverable from one specification mechanism can be used to drive deliverables which use another specification mechanism. Similarly activities from one methodology can be used to trigger activities of other methodology. If we achieve this, as an industry, it will be a great leap forward. (MOF - meta object facility by OMG, is close enough example of an interoperability standard).
Or if we are lucky a dominant de facto standard may evolve in every domains of discourse. And if it is far superior to any competing ones, as had happened in case of RDBMS and SQL, then it can become a de jure standard.
So however appealing the idea of compliance to well defined standards, I am afraid we have to learn to manage myriad of different standards and help them co-exist.
Wednesday, October 03, 2007
Wednesday, August 22, 2007
SOA Fable: Do you wear a watch?
Most of us wear watches, and except for those who wear it as a piece of jewellary, we expect a service from this piece of equipment. And what is the unique service provided by this equipment? It lets us know what time it is! Wait, hang on. Aren't there enough service providers, providing this very service, around us? Well every car has a clock in it. every house has many clocks, every PC has a clock. Even every mobile phone, PDA, iPhone has a clock. Why do people wear watches, anyway?
What are your expectation as a consumer from a possible service telling you waht time it is?
Availability: Service must be available when consumer needs it.
If a consumer relies only on mobile phone and battery runs out. The service is not available when consumer may need it.
Reliability: Service response must be reliable and should not require double checking.
A consumer is not sure of the time shown by a clock at public place, he needs to double check it with another reliable source anyway.
Accessibility: Consumer can access the service whenever he needs it.
A clock in laptop in backpack is not easily accessible in a crowded commuter train.
Trust: Consumer trusts that service is backed up by accountability on part of a service provider. When it is a question of life and death, one can trust service provided by one's own piece of equipment to be accurate, reliable and available than a general purpose service. As a consumer one tend to trust no one but oneself as most accountable service provider.
This is a very important insight which helps one prepare a proper versioning policy.
Without that trust versioning schemes can be mis-used for creating specialized services.
In enterprises, since SOA is mandated, project owners will use services. But they will make sure that they get their own private version of a service. This is quite easy by getting a veto power over life cycle of a service and mis-using governance for this sake. Assume a service version 1 is in use. Second consumer wants to create another version, because it has additional needs. This version 2 is derived from version 1. Now first consumer wants an upgrade to his existing service. But he is not willing to accept service version 2 as base for its next version. He will find any execuse to make sure he gets a service version 1.1 rather than 3. This pattern will keep repeating. And soon there will be a lot of versions, changing only in second qualifier. So you will get, what I call parversion (parallel version) anti-pattern.

SOA governance must make sure it guards against this anti-pattern and creates appropriate policies and controls to minimize and eliminate its occurences. Morover governance must recognise that this is a symptom and root cause lies somewhere else.
Moral of the story: Consumer is willing to bend rules to get an acceptable, reliable, accessible and trustworthy service. Watch out for such rules violation and fix root cause.
What are your expectation as a consumer from a possible service telling you waht time it is?
Availability: Service must be available when consumer needs it.
If a consumer relies only on mobile phone and battery runs out. The service is not available when consumer may need it.
Reliability: Service response must be reliable and should not require double checking.
A consumer is not sure of the time shown by a clock at public place, he needs to double check it with another reliable source anyway.
Accessibility: Consumer can access the service whenever he needs it.
A clock in laptop in backpack is not easily accessible in a crowded commuter train.
Trust: Consumer trusts that service is backed up by accountability on part of a service provider. When it is a question of life and death, one can trust service provided by one's own piece of equipment to be accurate, reliable and available than a general purpose service. As a consumer one tend to trust no one but oneself as most accountable service provider.
This is a very important insight which helps one prepare a proper versioning policy.
Without that trust versioning schemes can be mis-used for creating specialized services.
In enterprises, since SOA is mandated, project owners will use services. But they will make sure that they get their own private version of a service. This is quite easy by getting a veto power over life cycle of a service and mis-using governance for this sake. Assume a service version 1 is in use. Second consumer wants to create another version, because it has additional needs. This version 2 is derived from version 1. Now first consumer wants an upgrade to his existing service. But he is not willing to accept service version 2 as base for its next version. He will find any execuse to make sure he gets a service version 1.1 rather than 3. This pattern will keep repeating. And soon there will be a lot of versions, changing only in second qualifier. So you will get, what I call parversion (parallel version) anti-pattern.
SOA governance must make sure it guards against this anti-pattern and creates appropriate policies and controls to minimize and eliminate its occurences. Morover governance must recognise that this is a symptom and root cause lies somewhere else.
Moral of the story: Consumer is willing to bend rules to get an acceptable, reliable, accessible and trustworthy service. Watch out for such rules violation and fix root cause.
Sunday, July 15, 2007
Blogged for an year
It has been an year since I started to blog regularly (well at least once a month). The blog has given me a platform to express my ideas. I expected a lot of interaction with fellow professionals. That expectation has not been met, mainly because of my inability to continue conversations. Carrying out conversations over blogs need a lot of commitment. Balancing work, personal commitments and finding time for this activity been a challenge for me. For that reason I am in awe of bloggers who blog daily and on variety of subjects.
But whatever limited interactions I have had, opened my eyes to new ways of looking at things. I am ever thankful to blogosphere for enriching my professional life. I hope to meet some of my on-line acquaintances, whose thoughts I found insightful, in person. I also hope someone, somewhere might have found my thoughts useful and feels the same about me.
But whatever limited interactions I have had, opened my eyes to new ways of looking at things. I am ever thankful to blogosphere for enriching my professional life. I hope to meet some of my on-line acquaintances, whose thoughts I found insightful, in person. I also hope someone, somewhere might have found my thoughts useful and feels the same about me.
Subscribe to:
Posts (Atom)
Wednesday, October 03, 2007
Conform or co-exist?
This post suggesting a need for extreme standardisation needs to be discussed within industry. The idea of having extreme standardisation is extremely appealing but highly impractical. Pulls and counter-pulls within industry will make sure that there are always competing standards.
Vendors dont agree on Who decides on standardisation. There are multiple competing bodies even in standard setting space. Who decides what are the categories for standards? Should everything be in standard. That would imply commoditisation. What will vendors bring in as differentiation? There are no easy answers. If we ignore these questions then we will end up with surfeit of standards on top of existing mess.
As they said in vedic period "pinde pinde matirbhinna". Translated in English it means, every soul has different thinking. Implied in that is the notion that no thinking is superior or inferior, so who is to say which one should become standard? Each different specification mechanism or execution methodology is mostly in response to something desired by user community. So in some sense they represent user's aspirations (and vendor's motivations). How can these different motivations and aspirations be reconciled?
So what is the way out? Well there are ways of tackling these tricky questions.
For example instead of relying on extreme standardisation, industry bodies can work on interoperability standards. To do that, first thing as an industry we must agree on means to define categorisation and 'Domains of discourse'. We can then go on to develop interoperability standards for these various domains (intra domain as well as inter domain). Within IT there are various domains of discourse, for example if you consider IT change management category, the domains could be business strategy, IT strategy, portfolio planning, requirement & scoping, design & build, verification & validation, roll out & operational management, systems retirement etc. Similarly for different categorisation there will be different domains of discourse. Each of these domains will have many competing specification mechanisms and execution methodologies. What we need is means to interoperate between these specifications and methodologies for a domain of discourse and across domain of discourse.
With such interoperability standards in place the deliverable from one specification mechanism can be used to drive deliverables which use another specification mechanism. Similarly activities from one methodology can be used to trigger activities of other methodology. If we achieve this, as an industry, it will be a great leap forward. (MOF - meta object facility by OMG, is close enough example of an interoperability standard).
Or if we are lucky a dominant de facto standard may evolve in every domains of discourse. And if it is far superior to any competing ones, as had happened in case of RDBMS and SQL, then it can become a de jure standard.
So however appealing the idea of compliance to well defined standards, I am afraid we have to learn to manage myriad of different standards and help them co-exist.
Vendors dont agree on Who decides on standardisation. There are multiple competing bodies even in standard setting space. Who decides what are the categories for standards? Should everything be in standard. That would imply commoditisation. What will vendors bring in as differentiation? There are no easy answers. If we ignore these questions then we will end up with surfeit of standards on top of existing mess.
As they said in vedic period "pinde pinde matirbhinna". Translated in English it means, every soul has different thinking. Implied in that is the notion that no thinking is superior or inferior, so who is to say which one should become standard? Each different specification mechanism or execution methodology is mostly in response to something desired by user community. So in some sense they represent user's aspirations (and vendor's motivations). How can these different motivations and aspirations be reconciled?
So what is the way out? Well there are ways of tackling these tricky questions.
For example instead of relying on extreme standardisation, industry bodies can work on interoperability standards. To do that, first thing as an industry we must agree on means to define categorisation and 'Domains of discourse'. We can then go on to develop interoperability standards for these various domains (intra domain as well as inter domain). Within IT there are various domains of discourse, for example if you consider IT change management category, the domains could be business strategy, IT strategy, portfolio planning, requirement & scoping, design & build, verification & validation, roll out & operational management, systems retirement etc. Similarly for different categorisation there will be different domains of discourse. Each of these domains will have many competing specification mechanisms and execution methodologies. What we need is means to interoperate between these specifications and methodologies for a domain of discourse and across domain of discourse.
With such interoperability standards in place the deliverable from one specification mechanism can be used to drive deliverables which use another specification mechanism. Similarly activities from one methodology can be used to trigger activities of other methodology. If we achieve this, as an industry, it will be a great leap forward. (MOF - meta object facility by OMG, is close enough example of an interoperability standard).
Or if we are lucky a dominant de facto standard may evolve in every domains of discourse. And if it is far superior to any competing ones, as had happened in case of RDBMS and SQL, then it can become a de jure standard.
So however appealing the idea of compliance to well defined standards, I am afraid we have to learn to manage myriad of different standards and help them co-exist.
Wednesday, August 22, 2007
SOA Fable: Do you wear a watch?
Most of us wear watches, and except for those who wear it as a piece of jewellary, we expect a service from this piece of equipment. And what is the unique service provided by this equipment? It lets us know what time it is! Wait, hang on. Aren't there enough service providers, providing this very service, around us? Well every car has a clock in it. every house has many clocks, every PC has a clock. Even every mobile phone, PDA, iPhone has a clock. Why do people wear watches, anyway?
What are your expectation as a consumer from a possible service telling you waht time it is?
Availability: Service must be available when consumer needs it.
If a consumer relies only on mobile phone and battery runs out. The service is not available when consumer may need it.
Reliability: Service response must be reliable and should not require double checking.
A consumer is not sure of the time shown by a clock at public place, he needs to double check it with another reliable source anyway.
Accessibility: Consumer can access the service whenever he needs it.
A clock in laptop in backpack is not easily accessible in a crowded commuter train.
Trust: Consumer trusts that service is backed up by accountability on part of a service provider. When it is a question of life and death, one can trust service provided by one's own piece of equipment to be accurate, reliable and available than a general purpose service. As a consumer one tend to trust no one but oneself as most accountable service provider.
This is a very important insight which helps one prepare a proper versioning policy.
Without that trust versioning schemes can be mis-used for creating specialized services.
In enterprises, since SOA is mandated, project owners will use services. But they will make sure that they get their own private version of a service. This is quite easy by getting a veto power over life cycle of a service and mis-using governance for this sake. Assume a service version 1 is in use. Second consumer wants to create another version, because it has additional needs. This version 2 is derived from version 1. Now first consumer wants an upgrade to his existing service. But he is not willing to accept service version 2 as base for its next version. He will find any execuse to make sure he gets a service version 1.1 rather than 3. This pattern will keep repeating. And soon there will be a lot of versions, changing only in second qualifier. So you will get, what I call parversion (parallel version) anti-pattern.

SOA governance must make sure it guards against this anti-pattern and creates appropriate policies and controls to minimize and eliminate its occurences. Morover governance must recognise that this is a symptom and root cause lies somewhere else.
Moral of the story: Consumer is willing to bend rules to get an acceptable, reliable, accessible and trustworthy service. Watch out for such rules violation and fix root cause.
What are your expectation as a consumer from a possible service telling you waht time it is?
Availability: Service must be available when consumer needs it.
If a consumer relies only on mobile phone and battery runs out. The service is not available when consumer may need it.
Reliability: Service response must be reliable and should not require double checking.
A consumer is not sure of the time shown by a clock at public place, he needs to double check it with another reliable source anyway.
Accessibility: Consumer can access the service whenever he needs it.
A clock in laptop in backpack is not easily accessible in a crowded commuter train.
Trust: Consumer trusts that service is backed up by accountability on part of a service provider. When it is a question of life and death, one can trust service provided by one's own piece of equipment to be accurate, reliable and available than a general purpose service. As a consumer one tend to trust no one but oneself as most accountable service provider.
This is a very important insight which helps one prepare a proper versioning policy.
Without that trust versioning schemes can be mis-used for creating specialized services.
In enterprises, since SOA is mandated, project owners will use services. But they will make sure that they get their own private version of a service. This is quite easy by getting a veto power over life cycle of a service and mis-using governance for this sake. Assume a service version 1 is in use. Second consumer wants to create another version, because it has additional needs. This version 2 is derived from version 1. Now first consumer wants an upgrade to his existing service. But he is not willing to accept service version 2 as base for its next version. He will find any execuse to make sure he gets a service version 1.1 rather than 3. This pattern will keep repeating. And soon there will be a lot of versions, changing only in second qualifier. So you will get, what I call parversion (parallel version) anti-pattern.
SOA governance must make sure it guards against this anti-pattern and creates appropriate policies and controls to minimize and eliminate its occurences. Morover governance must recognise that this is a symptom and root cause lies somewhere else.
Moral of the story: Consumer is willing to bend rules to get an acceptable, reliable, accessible and trustworthy service. Watch out for such rules violation and fix root cause.
Sunday, July 15, 2007
Blogged for an year
It has been an year since I started to blog regularly (well at least once a month). The blog has given me a platform to express my ideas. I expected a lot of interaction with fellow professionals. That expectation has not been met, mainly because of my inability to continue conversations. Carrying out conversations over blogs need a lot of commitment. Balancing work, personal commitments and finding time for this activity been a challenge for me. For that reason I am in awe of bloggers who blog daily and on variety of subjects.
But whatever limited interactions I have had, opened my eyes to new ways of looking at things. I am ever thankful to blogosphere for enriching my professional life. I hope to meet some of my on-line acquaintances, whose thoughts I found insightful, in person. I also hope someone, somewhere might have found my thoughts useful and feels the same about me.
But whatever limited interactions I have had, opened my eyes to new ways of looking at things. I am ever thankful to blogosphere for enriching my professional life. I hope to meet some of my on-line acquaintances, whose thoughts I found insightful, in person. I also hope someone, somewhere might have found my thoughts useful and feels the same about me.
Subscribe to:
Posts (Atom)