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

[Dave Froble]

On 8/21/2018 10:12 PM, Kerry Main wrote:

>> The biggest change is in people's thinking. Getting the various parties to
>> come to grips that they cannot lay claim to the underlining
> infrastructure.
>> Everything is a service, the OS being offered, the DB instances,

While I'm aware that there are many methods for skinning the proverbial 
cat, I do think that it's a matter of semantics, and that things could 
mostly be considered a "service".

> networking
>> (although this is a work in progress, virtual load balancing is tricky),
> logging is
>> also a service, in-depth workload metrics (there are standard offerings
> that
>> come with every deployment but if you want extra you order it as a service
>> offering)
>>
>
> 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.

I'd address this specific case by having App B coordinate with Group1 
for App B group to implement the additions.  Still have the one service, 
if that's appropriate.

However, I'm a firm believer in modularity, and, perhaps two services, 
each specific to their requirements, just might be a better solution. 
Keep things simple.  KISS!  Just having many applications is not a bad 
thing.  Does violate KISS.