[Info-vax] Should VSI create a modern day VMS applications book ?

[Arne Vajhøj]

On 8/21/2018 10:12 PM, Kerry Main wrote:
> Reality check for the "everything is a service" (aka SOA).
> 
> Again, its not technical.
> 
> Sample issue:
> App A uses serviceA created by Group1. No issues.
> App B finds serviceA lacking in some way. Requests Group1 add functionality
> to ServiceA.
> Group1 says "good idea, but its not our priority right now. We will do it in
> next years release"
> AppB group says "not good enough". AppB writes their own service to address
> their specific requirements.
> 
> Result - you end up with hundreds/thousands of overlapping or similar
> functionality services - how do you manage the complexity and/or keep track
> of these across all of the various App/Infrastructure support groups??

s/service/library/w

 > Sample issue:
 > App A uses libraryA created by Group1. No issues.
 > App B finds libraryA lacking in some way. Requests Group1 add 
functionality
 > to LibraryA.
 > Group1 says "good idea, but its not our priority right now. We will 
do it in
 > next years release"
 > AppB group says "not good enough". AppB writes their own library to 
address
 > their specific requirements.
 >
 > Result - you end up with hundreds/thousands of overlapping or similar
 > functionality librarys - how do you manage the complexity and/or keep 
track
 > of these across all of the various App/Infrastructure support groups??

My claim will be that:
* almost all developers have seen a library get cloned and hacked
   like this
* very few developers will argue that common library is a bad
   idea due to this

s/library/service/w

:-)

Arne