Microservices Expo Authors: Elizabeth White, Pat Romanski, Gordon Haff, John Katrick, Mehdi Daoudi

Related Topics: Microservices Expo

Microservices Expo: Article

Knowing When to Use Web Services

Knowing When to Use Web Services

Web services are moving from the latest buzzword to a mature and accepted technology. Mainstream companies such as Eastman Chemical, Wells Fargo, and NEC have begun deploying significant Web Services-Based Integration (WSBI) projects. Avnet Computer Marketing (Avnet CM) is one of many companies also betting heavily on Web services. This month, "Web Services in the Real World" describes Avnet CM's strategic foray into WSBI (see sidebar). We'll explore their business objectives, why they chose Web services for some parts of their architecture (and not others), and the results they achieved.

Avnet Computer Marketing (Avnet CM) markets enterprise technology products from the world's premier computer manufacturers and software suppliers. Customers include value-added resellers (VARs) and enterprise customers, and Avnet CM provides them with marketing support, pricing strategies, and supplier-relationship management. Avnet CM is an operating group of Avnet, Inc. (NYSE:AVT), a Phoenix, Ariz.-based Fortune 500 company. Avnet is a technology marketing and services provider, and one of the world's largest distributors of electronic components and computer products from industry leading manufacturers.

The Challenge
Avnet CM manages Avnet's Hall-Mark e-business portal that allows customers and suppliers to configure and place orders, retrieve real-time pricing and availability information for products, and view their order status.

To provide customers and suppliers with a broad range of online services, Avnet CM needed to connect the portal to various back-end systems using a variety of protocols and file formats. "Maintaining this growing number of proprietary interfaces became untenable and prevented us from being able to respond quickly to new market opportunities," said Bud Alexander, vice president of Enterprise Integrated Solutions. He wanted to build a responsive IT infrastructure that allowed him to

  • Reduce the cost of development and maintenance by consolidating and standardizing internal system interfaces, and
  • Speed time to market by maximizing interface reuse.

    The Solution
    Alexander's strategy was to wrap applications with business-oriented WSDL interfaces, creating common business services, and then to pull data from multiple applications into one "Business Service Hub." (This is one of the usage patterns identified in the first article of this series, "Patterns in Web Services Projects"; WSJ, Vol. 3, issue 5). The goal was to consolidate interfaces and reduce the number of connections among systems. The architecture was required to maximize the potential for reuse, and the services had to be accessible from anywhere using any technology.

    With this framework in place, Alexander hoped to reduce system integration maintenance by combining and reusing connections among systems. Such a model would speed integration by reusing Web service components that were already built.

    The Architecture
    Three integrated portal applications, each developed and maintained by separate teams, provide the following capabilities to Avnet's sales force, customers, and suppliers:

  • Quote to Order: Intranet application used by Avnet sales to provide customers with product quotations and to expeditiously convert them to orders
  • Channel Connection: Customer portal that lets Avnet's authenticated VARs and customers retrieve real-time order status, leads, sales, credit history, and key performance information
  • Customer management: Internal portal that allows customer service representatives to centrally view and update customers' account information

    Avnet CM implemented the Business Service Hub with a Web services-based integration platform (see Figure 1). The portal applications communicate with this integration platform via SOAP to access data from the following back-end systems:

  • The IMS mainframe processes orders and performs other sales order management functions;
  • The operational data store (ODS) consolidates customer data to create a single view of the customer. The ODS is exposed as a simple set of Web services that aggregates information from a CRM system, database, mainframe, and external data from suppliers and manufacturers (using RosettaNet and EDI).


    The architecture also includes trading partner gateways for processing orders. Avnet CM currently supports RosettaNet and EDI transactions, and is planning to add a SOAP gateway in the future.

    Why Web Services?
    Avnet CM used Web services between the portal and the integration platform for the following reasons:

  • Simplicity: Even nonprogrammers are able to assemble Web service-based integration solutions using the integration platform tools. According to Alexander, "Users do not need expertise in SOAP or WSDL, so I don't need to hire senior messaging experts to develop integration services. I could put anyone on my integration team, no matter what their experience level, onto Web services projects." In addition, the portal's application server can readily consume SOAP messages. This made the integration easier, faster, and cheaper.
  • Abstraction: The portal team is organizationally separate from the IT team, which owns the back-end systems. The IT team wanted to make it easy for the portal team (and others in the future) to access information without having to know about the complexities and data formats of the back-office. "The portal content team can focus on the presentation layer and need not be proficient in databases, mainframes, and CRM systems. They simply call a Web service using whatever technology they already know," says Alexander. The contract between the teams is the WSDL interface.
  • Reusability: Reuse was critical. Other teams needed to access the same capabilities. Once a connection has been made and exposed as a Web service, it's easy to connect other applications.
  • Performance and reliability: Even though Avnet CM processes a high volume of orders from their web site, they found performance to be satisfactory. Alexander adds that they have never lost a single order.

    These reasons for using Web services are consistent with why other companies said they chose Web services for integration (see "Why Web Services Work"; WSJ, Vol. 3, issue 7). Interestingly, Alexander did not use Web services for the entire project. Specifically, his team did not use Web services between the integration layer and the mainframe and CRM systems. Instead, they used adapters and native APIs. Here's why:

  • Back-end ownership: Alexander's group is responsible for the back-end systems they are integrating with. This means they had the necessary domain expertise, had direct access to these systems, and could control the technology to access these systems. Web services, on the other hand, are better at facilitating the integration between different organizations because they provide an abstraction layer, define a contract (the WSDL interface) between the groups, and let each group use whatever technology they want to access the interface.
  • Lack of SOAP support: The mainframe's SOAP support was inadequate. The CRM systems actually consisted of four separate applications, and not every one of these had native SOAP support. On the other hand, the four systems all supported APIs and adapters.
  • Performance and reliability requirements could not be satisfied with Web services: Each service consisted of a complex set of transactions on the back end that required transactional integrity, which was managed by the integration platform.
  • No reuse required: The mainframe and CRM APIs were never meant to be accessed directly. Thus, reusing the APIs directly was not a requirement. They were instead rolled up into composite applications that were exposed to the outside world as a simpler set of Web services that were meant for reuse.

    The Results
    With Web services connecting several back-end systems with their portal applications, Avnet CM realized the following benefits:

  • Reduced cost of maintaining and extending the integration architecture by consolidating the interfaces and standardizing on Web services. Avnet CM has been able to successfully retire their proprietary interfaces (custom XML, FTP, and IP sockets) in favor of Web services.
  • Faster time to market with improved IT agility. New projects are now measured in days instead of weeks. Previously, integrating the quote-to-order application with the IMS mainframe required approximately six weeks. But, because the Web service was already built, connecting the order entry e-business system took only one day.

    What's Next
    In the future, Avnet CM will extend the Web services framework to its customers and suppliers. "Web services continue to be central to our IT strategy. The investment in our Web serviced-based integration platform allows us to take advantage of our IT investments and to deliver greater value for the company," concludes Alexander.

    Companies like Avnet CM prove that Web services are maturing as an accepted technology. At the same time, it's clear that Web services are not the silver bullet to solving complex integration problems, either. The trick is figuring out when to use Web services, and when not to. Based on the ROI realized by Avnet and other customers profiled in this column, Web services, and the service-oriented architectures that support them, are increasingly becoming a key component of any successful company's integration strategy.

    Avnet CM turns to Web Services

    Customer: Avnet Computer Marketing is an operating group of Avnet, Inc. (NYSE:AVT), a Phoenix, Ariz.-based Fortune 500 company. Avnet is a technology marketing and services provider and one of the world's largest distributors of electronic components and computer products from industry leading manufacturers.

    Challenge: Consolidate and standardize application interfaces; implement a service-oriented integration architecture to speed time to market.

    Solution: Avnet's e-business portal allows customers and suppliers to configure and place orders, retrieve real-time pricing & availability information, and view their order status. Web Services-Based Integration (WSBI) feeds the portal with data from various back-end systems.

    Why Web Services: Avnet chose WSBI primarily for three reasons:

    • Simplicity
    • Reusability
    • Abstraction
    Key Business Benefits: By using WSBI, Avnet benefits from:
    • Reduced development and maintenance cost
    • IT agility
    • Faster time to market
  • More Stories By Michael Blank

    Michael Blank is a founding member of webMethods, Inc. and was its first software engineer. During his tenure, he has started and commercialized several product offerings. As director of developer marketing, he manages webMethods’ developer communities as well as the software evaluation program (http://evals.webmethods.com).

    Comments (2) View Comments

    Share your thoughts on this story.

    Add your comment
    You must be signed in to add a comment. Sign-in | Register

    In accordance with our Comment Policy, we encourage comments that are on topic, relevant and to-the-point. We will remove comments that include profanity, personal attacks, racial slurs, threats of violence, or other inappropriate material that violates our Terms and Conditions, and will block users who make repeated violations. We ask all readers to expect diversity of opinion and to treat one another with dignity and respect.

    Most Recent Comments
    Michael Blank 12/02/03 12:38:59 PM EST

    Below is the response from Avnet:

    1. Did you use Trading Networks to use webservices ? or you have exposed
    webservices to the partner directly ?

    The external facing web services are exposed to to our partners via a UDDI server which allow for anonymous browsing of services. We do not use Trading Networks to manage Avnet's web services environment.

    2. Do you suggest me to use WebServices or Trading Networks for the batch
    customer processing coming in single XML document ? Please let me know what
    your views on this.

    Trading Networks natively will handle XML documents via it's 'receive' service. Once it is received the document can then be processed and routed via the routing rules that are associated with the document. In the case of batch processing you could route the request to a service that would break it apart to be processed as individual transactions. Web Services have a role of transporting the document and Trading Networks have a role of managing the documents once they are received or submitted.

    naveen kenche 11/20/03 03:14:47 PM EST

    Hi!, I understood the way you have used webservices from the external clients. My questions are as follows.
    1. Did you use Trading Networks to use webservices ? or you have exposed webservices to the partner directly ?
    2. Do you suggest me to use WebServices or Trading Networks for the batch customer processing coming in single XML document ? Please let me know what your views on this.
    Thanks and Regards

    @MicroservicesExpo Stories
    "We started a Master of Science in business analytics - that's the hot topic. We serve the business community around San Francisco so we educate the working professionals and this is where they all want to be," explained Judy Lee, Associate Professor and Department Chair at Golden Gate University, in this SYS-CON.tv interview at 21st Cloud Expo, held Oct 31 – Nov 2, 2017, at the Santa Clara Convention Center in Santa Clara, CA.
    There is a huge demand for responsive, real-time mobile and web experiences, but current architectural patterns do not easily accommodate applications that respond to events in real time. Common solutions using message queues or HTTP long-polling quickly lead to resiliency, scalability and development velocity challenges. In his session at 21st Cloud Expo, Ryland Degnan, a Senior Software Engineer on the Netflix Edge Platform team, will discuss how by leveraging a reactive stream-based protocol,...
    We call it DevOps but much of the time there’s a lot more discussion about the needs and concerns of developers than there is about other groups. There’s a focus on improved and less isolated developer workflows. There are many discussions around collaboration, continuous integration and delivery, issue tracking, source code control, code review, IDEs, and xPaaS – and all the tools that enable those things. Changes in developer practices may come up – such as developers taking ownership of code ...
    The dynamic nature of the cloud means that change is a constant when it comes to modern cloud-based infrastructure. Delivering modern applications to end users, therefore, is a constantly shifting challenge. Delivery automation helps IT Ops teams ensure that apps are providing an optimal end user experience over hybrid-cloud and multi-cloud environments, no matter what the current state of the infrastructure is. To employ a delivery automation strategy that reflects your business rules, making r...
    Cloud Governance means many things to many people. Heck, just the word cloud means different things depending on who you are talking to. While definitions can vary, controlling access to cloud resources is invariably a central piece of any governance program. Enterprise cloud computing has transformed IT. Cloud computing decreases time-to-market, improves agility by allowing businesses to adapt quickly to changing market demands, and, ultimately, drives down costs.
    For over a decade, Application Programming Interface or APIs have been used to exchange data between multiple platforms. From social media to news and media sites, most websites depend on APIs to provide a dynamic and real-time digital experience. APIs have made its way into almost every device and service available today and it continues to spur innovations in every field of technology. There are multiple programming languages used to build and run applications in the online world. And just li...
    The general concepts of DevOps have played a central role advancing the modern software delivery industry. With the library of DevOps best practices, tips and guides expanding quickly, it can be difficult to track down the best and most accurate resources and information. In order to help the software development community, and to further our own learning, we reached out to leading industry analysts and asked them about an increasingly popular tenet of a DevOps transformation: collaboration.
    Modern software design has fundamentally changed how we manage applications, causing many to turn to containers as the new virtual machine for resource management. As container adoption grows beyond stateless applications to stateful workloads, the need for persistent storage is foundational - something customers routinely cite as a top pain point. In his session at @DevOpsSummit at 21st Cloud Expo, Bill Borsari, Head of Systems Engineering at Datera, explored how organizations can reap the bene...
    How is DevOps going within your organization? If you need some help measuring just how well it is going, we have prepared a list of some key DevOps metrics to track. These metrics can help you understand how your team is doing over time. The word DevOps means different things to different people. Some say it a culture and every vendor in the industry claims that their tools help with DevOps. Depending on how you define DevOps, some of these metrics may matter more or less to you and your team.
    "CA has been doing a lot of things in the area of DevOps. Now we have a complete set of tool sets in order to enable customers to go all the way from planning to development to testing down to release into the operations," explained Aruna Ravichandran, Vice President of Global Marketing and Strategy at CA Technologies, in this SYS-CON.tv interview at DevOps Summit at 21st Cloud Expo, held Oct 31 – Nov 2, 2017, at the Santa Clara Convention Center in Santa Clara, CA.
    "We are an integrator of carrier ethernet and bandwidth to get people to connect to the cloud, to the SaaS providers, and the IaaS providers all on ethernet," explained Paul Mako, CEO & CTO of Massive Networks, in this SYS-CON.tv interview at 21st Cloud Expo, held Oct 31 – Nov 2, 2017, at the Santa Clara Convention Center in Santa Clara, CA.
    "Grape Up leverages Cloud Native technologies and helps companies build software using microservices, and work the DevOps agile way. We've been doing digital innovation for the last 12 years," explained Daniel Heckman, of Grape Up in this SYS-CON.tv interview at 21st Cloud Expo, held Oct 31 – Nov 2, 2017, at the Santa Clara Convention Center in Santa Clara, CA.
    "NetApp's vision is how we help organizations manage data - delivering the right data in the right place, in the right time, to the people who need it, and doing it agnostic to what the platform is," explained Josh Atwell, Developer Advocate for NetApp, in this SYS-CON.tv interview at 20th Cloud Expo, held June 6-8, 2017, at the Javits Center in New York City, NY.
    "Outscale was founded in 2010, is based in France, is a strategic partner to Dassault Systémes and has done quite a bit of work with divisions of Dassault," explained Jackie Funk, Digital Marketing exec at Outscale, in this SYS-CON.tv interview at 20th Cloud Expo, held June 6-8, 2017, at the Javits Center in New York City, NY.
    "I focus on what we are calling CAST Highlight, which is our SaaS application portfolio analysis tool. It is an extremely lightweight tool that can integrate with pretty much any build process right now," explained Andrew Siegmund, Application Migration Specialist for CAST, in this SYS-CON.tv interview at 21st Cloud Expo, held Oct 31 – Nov 2, 2017, at the Santa Clara Convention Center in Santa Clara, CA.
    Let's do a visualization exercise. Imagine it's December 31, 2018, and you're ringing in the New Year with your friends and family. You think back on everything that you accomplished in the last year: your company's revenue is through the roof thanks to the success of your product, and you were promoted to Lead Developer. 2019 is poised to be an even bigger year for your company because you have the tools and insight to scale as quickly as demand requires. You're a happy human, and it's not just...
    The enterprise data storage marketplace is poised to become a battlefield. No longer the quiet backwater of cloud computing services, the focus of this global transition is now going from compute to storage. An overview of recent storage market history is needed to understand why this transition is important. Before 2007 and the birth of the cloud computing market we are witnessing today, the on-premise model hosted in large local data centers dominated enterprise storage. Key marketplace play...
    Cavirin Systems has just announced C2, a SaaS offering designed to bring continuous security assessment and remediation to hybrid environments, containers, and data centers. Cavirin C2 is deployed within Amazon Web Services (AWS) and features a flexible licensing model for easy scalability and clear pay-as-you-go pricing. Although native to AWS, it also supports assessment and remediation of virtual or container instances within Microsoft Azure, Google Cloud Platform (GCP), or on-premise. By dr...
    With continuous delivery (CD) almost always in the spotlight, continuous integration (CI) is often left out in the cold. Indeed, it's been in use for so long and so widely, we often take the model for granted. So what is CI and how can you make the most of it? This blog is intended to answer those questions. Before we step into examining CI, we need to look back. Software developers often work in small teams and modularity, and need to integrate their changes with the rest of the project code b...
    Kubernetes is an open source system for automating deployment, scaling, and management of containerized applications. Kubernetes was originally built by Google, leveraging years of experience with managing container workloads, and is now a Cloud Native Compute Foundation (CNCF) project. Kubernetes has been widely adopted by the community, supported on all major public and private cloud providers, and is gaining rapid adoption in enterprises. However, Kubernetes may seem intimidating and complex ...