So, as in the other thread, what do you think about using BEI? H.Ozawa
--- In [email protected], Gregg Wonderly <ge...@...> wrote: > > htshozawa wrote: > > That's exactly why we should stick with SOA instead of changing names. > > Changing names seems like we were defeated or worse, that we are just > > trying to sell the same of stuff under a different name. The point is > > there were some (many?) initiatives/projects that went sour but if we > > were a used car dealer, would we change the name because the dealership > > across the street is selling lots of lemons? > > Have you been to a KFC (Kentucky Friend Chicken) restaurant lately? It may > soon > be KBC (Kentucky Baked Chicken) or just KC that are the initials for the > company. Fried food is bad for the masses, in general, and getting Fried out > of > the name is not such a bad thing. > > At some point, we have to decide that SOA doesn't really describe anything > tangible. It doesn't spell out the things that help people understand what > to > do where and how. It says why and when, but people already know what they've > done, where they did and how they did it. And they know it's not working > now, > and many can even see why it's not working. But, the only way to establish a > "what, where and how" is to decide on some technically based solutions and > deploy them. > > The missing specifics, because of too many technologies and related, yet > incompatible standards keep people from being successful unless they hire an > expert that can learn where they are at, and then plot the course to where > they > need to be. Only after understanding all the technologies, could one > possibly > make the "best" choice. > > Usually that's a lot more work than your boss will pay you for, or has time > for > you to learn, so whatever appears closest to working first is what people > will > elect to use. > > The regular emails to this list that say "I'm converting our software to an > SOA, > what do I need to download and use" pretty much spell out the simple > expectations that many people have, and the fact that they are most likely > going > to fail many times because everyone will tell them something different that > seems to all fit together until you get down to the actual integration and > find > out that this one speaks JMS and that one speaks .Net and this one over here > provides HTTP access and yields XML documents and... > > Gregg Wonderly >
