Consumer Driven IT: Accept Imitations, but Not Limitations

There is a tremendous amount of software development going on in large enterprises today.

atmosphere-arrowsThere is a tremendous amount of software development going on in large enterprises today. Customers often joke that they have more developers on staff than Oracle or Microsoft.

But none of this software is developed in isolation. Ask developers, and they’ll tell you that the infrastructure they have to deal with is more complex and interdependent than ever before. In truth, much of software development is in fact an integration effort. IT development teams are building for myriad front-end web and mobile platforms, while also bringing along everything else the company has ever done. Enterprise development today relies on an increasing number of continually changing apps, data sources, everything as a service (IaaS, PaaS, SaaS, etc.), and integration middleware to play nicely with the real world and work properly for the organization.

Getting all of these distributed systems to an available and stable state for development and testing is like aligning the stars – it is nearly impossible. This lack of stable and available resources creates constraints that delay or prevent successful application deployments.

As an example of what companies face today, an IT leader at a large financial institution recently told me about a process his organization goes through three times a year. He’s dubbed it “enterprise release,” and it involves hundreds of applications, all pushed live simultaneously. These applications—some homegrown, some off-the-shelf, all highly customized—might address thousands of business and technical requirements. But none of the components can be effectively tested against any other systems, because nothing is ever really finished or ready at the same time, so they simply drop functionality out of each release. A development manager at the company summed up the situation this way: “I can’t do anything until I have everything, but I never have everything.”

These guys tried to create copies of production at huge expense, but that never provided enough stability for reliable results. The performance lab environment wouldn’t provide more than 10 percent of the peak production load, so there’s no chance to test for scalability. The code can’t be tested against specialized data scenarios they need, because there’s no DBA access to the data (e.g. where a specific customer scenario might be entered to give triple reward points after her third card purchase at a grocery store).

Sadly, that large financial institution is not alone. I’m sure many readers are nodding in agreement, having experienced similar less-than-ideal development scenarios that arise as a result of consumer-driven IT demands in a distributed software world. The goal of faster delivery drives many companies to implement software changes without forward visibility due to constraints in the environment. In the end, deadlines are missed, the IT organization’s reputation is further diminished, and in some cases (especially with well-known brands and public-facing applications), well-publicized failures make headlines. How can all of us in the business of developing software fix this problem, wherever we work?
We need to accept imitations, not limitations.

Unlike virtually all other manufacturing disciplines, the software development industry typically doesn’t validate its products in a simulator before finalizing and shipping its designs. Can you imagine Boeing taking an experimental wing, bolting it on an airplane in San Francisco, and seeing how well it works on the next scheduled flight to New York?

No, Boeing engineers wouldn’t dream of using the real thing. They test designs using a flight simulator and a wind tunnel, where any condition, from rainy days to high winds can be simulated. In the same way, enterprise software should be engineered and tested using service virtualization, which simulates an application’s surrounding real-world environment, data scenarios, and workload.

Service virtualization “listens” to applications and the messages passed between systems. It then clones those underlying systems in a stable, scalable virtual service environment for software development teams to use. A service virtualization platform such as CA LISA behaves and reacts just like the actual production systems being updated, integrated, or otherwise leveraged. Virtual services can be infinitely customized and used by multiple development teams at the same time.

The result is the polar opposite of what most companies dealing with complex IT landscapes are experiencing today: faster time to market (with few, if any, missed deadlines, planned rationally); lower development costs; and few or no embarrassing defects and performance issues escaping into production to vex end users and customers alike.

With the competition just a click away, isn’t it time for software development to behave more like a real engineering discipline? It’s time we embraced simulation to prove, perfect, and deliver new business and technical functionality without limitations.

Written by

John Michelsen

CA Leadership

As CTO, John is responsible for technical leadership and innovation at CA. He is also…

Published in


View this topic
  • James Holland

    This is great. Hooray for Disney’s imagineers!


    become a new brand in the share market research with its accurate research. Proven
    itself always right whether market is bull or bear. Last week all paid clients
    booked handsome profit in NIFTY, BANKINIFTY & STOCKS. Now for the coming
    week we expect more correction can come in NIFTY as the IRAQ issue is getting
    more tense, If it happens more then you will see a sharp fall in all world marketNSE BSE, STOCK TIPSbecause as we know all world run on
    crude & most of the crude comes from IRAQ. So be ready for a sharp fall so
    sell will be the best strategy for next week also. Traders can make a sell
    position in NIFTY around 7600-7650 with stoploss 7750 for the target of
    7300-7200.One can also make a sell call NIFTY 50 stocks as per NIFTY levels. You
    can also take our two days free trial to check our accuracy. For further updates
    you can visit our website.



  • king lear

    testing comment functionality, please do not publish this

  • Rachel Macik

    Love the personal pic :)

    • CAHighlight

      Thank you!

  • Plutora Inc

    This is a good case study. 2.3 sec’s off a login transaction is big.

  • Michele Hudnall

    While the analysts were hyping DevOps, I posted the oversight of not including security as part of that discussion as you are highlighting here. Instead of just talking DevOps, it should be DOS (what’s old is new again :-) – DevOpsSec. As a previous AppDev person, it’s the app, who’s using it, why and where rather than the device and having the service available.

    As you rightly point, out Security should be baked into the solution.

    Nice Post and Timely!


    • CAHighlight

      Thank you for your feedback Michele. Agreed – security cannot be overlooked. Appreciate your input!

  • Mitesh

    I would love a printed copy

  • Lars Johansson

    I love the idea of BYOID! This makes me choose if I am almost anonymous (with my Hotmail Nicname) or official with identity from an official organisation. My Identity Provider will attach identity with right level of LoA according to the need of the Service provider.

    • CAHighlight

      Thank you for your comment. BYOID has tangible benefits for end users and relying parties but it also has to be weighed in the balance with potential risks and liability concerns. It will be interesting to see how BYOID plays out in the enterprise.