Your definitions of - and comparisons between - SOA and Enterprise 2.0 Social Software identify some important differences. It seems to me that for the true potential of Enterprise 2.0 to emerge, business leaders need to be educated and be willing to support/admit the value of freeform social software as an enterprise software tool that delivers real personal and team productivity gains.
Do have any case studies or examples that could help illustrate the impact that enterprise class social software has on personal and/or team productivity?
Randall Cronk
· 3 years ago
"Even SOA proponents agree that there's no recent tech breakthroughs that make it a more achievable vision now than it was before . . . "
I disagree. You might check out space-based virtualization schemes like that of my client GigaSpaces. They encapsulate both middleware and legacy apps in dynamically extensible runtime environments that talk to each other via a JavaSpaces implementation. You can pretty much turn anything into a service without doing a major rewrite or creating a lot of upfront rules. Given that kind of freedom, you might find SOA and Enterprise 2.0 more philosophically in tune than is first apparent. See my post here: http://www.greatwriting.com/blog/2006/05/soa-is...
Tomasz
· 3 years ago
Your definitions of - and comparisons between - SOA and Enterprise 2.0 Social Software identify some important differences. It seems to me that for the true potential of Enterprise 2.0 to emerge, business leaders need to be educated and be willing to support/admit the value of freeform social software as an enterprise software tool that delivers real personal and team productivity gains.
Paul Reeves
· 3 years ago
2 points: 1. unstructured data invites a non-egalitarian system as it discourages usage by people unable to quickly and effectively parse poorly written text (good writing is revision and sweat).
2. Structures evolve from previous structures. I do not think they emerge. The lack of structure in data means the data is not useful in the enterprise. Enterprise wikis, for example, should provide configurable structures and workflows for data to be truly useful. Provide a decision making template that groups can use to propose, debate, select and monitor a policy over time and you have a killer app. As long as the structure provides for basic and complex data types, it can evolve as necessary.
kris
· 2 years ago
The reason this is so confusing is the use of ORIENTED in the TLA. WhatÂ’s that about? Is it akin to some form of IT sexual orientation? Is it an optional response? WTF does it mean?? IMO it should be services BASED architecture. Much easier to understand and closer to reality from what I see in the field.
All Comments
Your definitions of - and comparisons between - SOA and Enterprise 2.0 Social Software identify some important differences. It seems to me that for the true potential of Enterprise 2.0 to emerge, business leaders need to be educated and be willing to support/admit the value of freeform social software as an enterprise software tool that delivers real personal and team productivity gains.
Do have any case studies or examples that could help illustrate the impact that enterprise class social software has on personal and/or team productivity?
I disagree. You might check out space-based virtualization schemes like that of my client GigaSpaces. They encapsulate both middleware and legacy apps in dynamically extensible runtime environments that talk to each other via a JavaSpaces implementation. You can pretty much turn anything into a service without doing a major rewrite or creating a lot of upfront rules. Given that kind of freedom, you might find SOA and Enterprise 2.0 more philosophically in tune than is first apparent. See my post here: http://www.greatwriting.com/blog/2006/05/soa-is...
1. unstructured data invites a non-egalitarian system as it discourages usage by people unable to quickly and effectively parse poorly written text (good writing is revision and sweat).
2. Structures evolve from previous structures. I do not think they emerge. The lack of structure in data means the data is not useful in the enterprise. Enterprise wikis, for example, should provide configurable structures and workflows for data to be truly useful. Provide a decision making template that groups can use to propose, debate, select and monitor a policy over time and you have a killer app.
As long as the structure provides for basic and complex data types, it can evolve as necessary.