--- In [email protected], Michael Poulin <[EMAIL PROTECTED]> wrote: > > <firing into the "milk"> stands for missing the target...
Thanks for the "new thing learned today!" > It is about misunderstanding of what SO is about from the project > management and testing team. It is not about applications. I am > saying - doing SO work, you have to think in SO all way down to > production. I get your meaning now, I think. > Nobody saying that apps would go away soon. I only question the > ability "to expose capabilities as services" by adding just a > publicly accessible interface. I believe, and all my experience > confirms it, that it is simply not enough. This is why I state that > a Web Services interface on a monolithic app does not make it a > service. Nothing more. Got ya. We agree. I hope I didn't post anything that indicated I was advocating that. > Not exactly. It may be a healthy app but we do not know about it up- > front. Finding a useful function in the app is a 1/2 of work. Now > we have to confirm that this function can properly work in SO > environment (retiring the rest of the app or not) - this is the > second 1/2 of work. For instance, in many cases, the knowledge of > the internal dependencies inside the app is lost in the company and > we may get surprises when call the function directly... We fundamentally agree. We need to understand the impact and implications fully. > > It seems to me that the > > issues should considered on a case-by-case basis. Some apps > > will play fine. Others will not. > > AGREE Yay! -Rob
