The ITKO Blog: Service Virtualization and Application Lifecycle Optimization - CA Technologies

SOA Best Practices: Continuous Testing and Validation

Several weeks back I gave you a real life experience that typified why our test strategy we call the Three C’s has Complete as one of those C’s. This blog will give you a different real-life experience on why Continuous deserves “C” status.

I was meeting with a Director of development at one of the worlds largest financial institutions. Many of their trading applications have absurd levels of complexity and variability along with, of course, radical performance expectations. Really cool stuff.

A certain critical service was running on a major SOA platform. The vendor released an update to that platform, and the team responsible for this service ran their unit and service level tests -- doing more than most teams I’ve seen. Turns out, they all passed, and in fact the service performed its main function 12 milliseconds faster -- COOL!

Then again, maybe not.

They deployed the patch and watched their entire currency trading system grind to a near halt!

Wait, you sped up the service and slowed down an application? Yes. Turns out the performance of the service prevented timing issues in the orchestration layer from surfacing in use by an application.

Of course it wasn’t obvious to the team that this was in fact the issue -- they were blaming the vendor, then their new code changes looking for how they could have wrecked the performance. They went on for days losing millions until they figured out what was really happening.

The Continuous C solves for this type of problem. Take those same tests you would automate at the orchestration and solution levels and run them on a continuous basis at those points of integration, pre-production. You’ll get immediate notice of this type of issue along with much clearer identification of the root cause.

Oracle buys BEA - Nice time to get a check-up

The biggest news in software may have already hit this year, but it's not like we didn't hear it coming for the past few months. Oracle finally makes good on its intent to buy BEA at $8.5B: http://online.wsj.com/article/SB120048691486294361.html

To us, this is good news -- like when SoftwareAG and webMethods merged - it combines a strong integration firm with a global presence, with a technology leader in the SOA space.

It's also a good move for Larry. Aside from increasing their customer base, it really moves Oracle more into the SOA mainstream - almost every customer we know has some Oracle apps, databases and integration inside their enterprise, but adding some leading AquaLogic ESB and Governance aspects of BEA will make a huge difference in advancing Oracle FUSION as an SOA platform.

Oracle getting JRockit from BEA also bodes well for performance, as now they can optimize that for the Oracle application stack.

For BEA customers, at least the anticipation is over, and they can continue to move forward with their plans with this reality in mind. I'm quite sure the best of BEA's stack will still be going on in the FUSION platform. Plus, for quality and reuse, consolidation of a SOAP stacks is a good thing. Both BEA and Oracle were operating their own SOAP stacks, and combining those particular efforts will create better interoperability for a whole lot of customers.

Is this too much consolidation? There are still several choices for how you provision SOA - you can go TIBCO, SoftwareAG/webMethods, IBM or HP, now Oracle/BEA, maybe Microsoft, or even open source, and there are best of breed tools out there that still perform unique functions in the SOA ecosystem. See, SOA is still something you DO, not something you buy. The business requirements should still lead the technology decision in every case -- and that doesn't usually jibe with the "one vendor fits all" strategy.

Where's the risk to BEA and Oracle customers? As a vendor charged with testing and validating platforms from both BEA and Oracle, this will create many new opportunities to help companies integrate and ensure business continuity as the story of consolidation continues to evolve.

We recommend that whatever your preferred tools are, that you follow best practices of creating a set of baseline component and system-wide tests of your "as-is" environment, so that as these two platforms are merged and upgraded, you will be able to test and maintain Business Continuity throughout the process. This is equally important if you decide to move to another vendor as well.

While we do believe that the combined new company will certainly make a commitment to customers, if you are in IT there is no shortcut to quality. Your best strategy is to establish a line of defense against unforeseen consequences -- with a thorough, and thoroughly managed suite of tests.

European SOA: Ahead of the Curve?

I'm in Germany right now, looking forward to a session at ZapThink's Practical SOA in Frankfurt event tomorrow. I'll be joining some peers from companies like T-Mobile, Swisscom, Novartis and SwissLife who are going to be sharing their own SOA success stories.

Why does SOA seem to be moving forward a little faster in Europe than in North America? We've posed these kinds of questions in our surveys and forums, and often it seems that stateside, the term "SOA" can polarize some IT teams - it's an "either/or" decision at the architectural level.

Talking to our EMEA director, Wilfred, he says part of the reason it seems adoption is high in Europe is that it SOA is often driven by developers working in smaller teams. Service-orientation can be started on a much smaller scale, and tested pragmatically before rollout to the larger organization. So, SOA there doesn't need to be an enterprise-level initiative in all cases, it can be something the company dabbles in before making a full commitment.

The upside of this pragmatic approach is that the SOA project can leverage some small wins to pay for a bigger commitment. The downside? Companies still need to beware of publishing services without a higher level of architectural coordination between teams.

This isn't to say that there aren't also companies in Europe starting from a strong enterprise architecture perspective and defining a top-down approach to SOA. I look forward to meeting both the pragmatists and the strategists this week!