Ten ways to tell it’s not SOA
Are we having fun yet? I’ve talked plenty about companies implementing JBOWS (Just a Bunch of Web Services) versus full-throttle SOA, but is there a way to tell the difference?
Here are a few clues that you may be not quite as service-enabled as you thought:
1) If a vendor tells you that you need to buy a suite to get to SOA… it’s not SOA. SOA means complete freedom from suites and integrated packages.
2) If a vendor is trying to sell you hardware… it’s not SOA. Enough said.
3) If you’re sending out email inquiries or making phone calls to find out what services are out there…. it’s not SOA. None of this registry/repository nonsense; why not just fire off an email to colleagues to see what might be out there that you can use in your own applications?
4) If nobody’s sharing services… it’s not SOA. You can have all the standardized services you can handle, but if it’s services within silos and nothing more, then it’s services in silos.
Resources for
