Microservices Expo Authors: Jason Bloomberg, Elizabeth White, Liz McMillan, Pat Romanski, Mehdi Daoudi

Related Topics: Microservices Expo

Microservices Expo: Article

Putting Web Services into (Business) Context

Putting Web Services into (Business) Context

Web services tool vendors frequently compete on how quickly their users can "generate a Web service from scratch" or "expose a Java/COM+/CORBA class as a Web service." While speed of development is important, the broader business needs of an enterprise must be the main driver of new technology adoption.

Blindly applying new technology ultimately results in more poorly conceived software. These applications are just as difficult to maintain as existing applications, only they're running on yet another technical infrastructure. As ZapThink, LLC, an XML- and Web services-focused industry analyst group, explains, "Just because a new technology has promise doesn't guarantee that it will be applied correctly."

So how do IT organizations move from "playing" with Web services development to providing truly useful services that support key business objectives? Companies must be able to view their existing software development assets (SDAs) within the context of the enterprise's strategic business processes in order to take full advantage of the promise of Web services. IT executives need to understand what assets exist, where they are located, and how each fits into the corporate business landscape, i.e. a model-based approach. This approach to Web services development gives enterprises an efficient way to enable existing SDAs as Web services; it can be broken into four steps - assess, build, locate, and employ.

Let's take a simple example - a currency conversion component - through this process.

Example Component - CurrencyExchange EJB
Our example component is an EJB that provides currency conversion services - converting dollars to euros, setting up conversion tables, and so on. Figure 1 presents this example component in UML, showing the external interfaces of the component without any of the implementation details involved in building the component.


The functional capabilities of this component are presented to its users via a SessionBean interface containing a number of method definitions. These methods place dependencies on two supporting elements of the external component definition: a set of transfer object types used to interchange nonprimitive data with the component, and a specialized exception that users of the component must handle when setting exchange rates into the component. Also, our CurrencyExchange component allows its users to control the conversion algorithm or algorithms used when converting one currency to another, both through a component configuration interface as well as by allowing the configured conversion strategy to be selectively overridden on a call-by-call basis.

Applying the enABLE Methodology
The four steps in our model-based approach are:

  • Assess what you have and create a business roadmap for migrating to Web services
  • Build a catalog of essential software development assets (SDAs) mapped to your business roadmap (i.e., your business architectures and models)
  • Locate the most appropriate software assets for your high-priority services using the catalog you have built
  • Employ these assets in your tools of choice for developing Web services

    A typical IT organization will have thousands of assets that have accumulated over the years. Assessing which of these assets are of value to the organization moving forward must incorporate both business and technical perspectives. Issues that need to be taken into account during the assessment phase include:

  • The technology used to build the asset
  • Compatibility of the asset's technology with future technical architectures being defined by the organization
  • Level of documentation (i.e., artifacts resulting from the software development process) available that describes the asset's business functionality
  • Current use of the asset to support the organization's business activities
  • Expected use of the asset to support future business needs

    As you begin, remember the 80/20 rule; some SDAs are obvious candidates for your initial cataloging efforts, while other marginal assets are best left behind.

    How does our example component fit against our assessment criteria?

  • Technology: Built using J2EE technology.
  • Future technical architectures: Our organization is in the process of defining a service-oriented architecture that includes Web services as a core element. These Web services will be implemented using a combination of J2EE component technology and adapter technology, which encapsulates legacy applications within our environment.
  • Level of documentation: Component artifacts include source code, a deployable .jar file, a UML model of the component that includes both an external client-oriented view as well as an internal design-oriented view, and javadoc.
  • Current use of asset: Component was built as part of a project to incorporate international capabilities into our order management application.
  • Expected use of asset: As our business expands its international capabilities, the need for a currency conversion service available to multiple departments has become clear.

    Based on our assessment, it appears that our currency conversion component is an important asset that should be preserved and managed into the future. This leads us to the next stage of our model-based approach.

    In the build phase, our task is to align our essential SDAs with our business roadmap (i.e., our business architectures and models describing current and future business requirements to be placed on the IT organization). The end result of this effort is a ready reference that gives us the ability to see what aspects of our business architecture are already supported, to identify redundancies, and to see where gaps exist. Ultimately, effective use of this reference model will enable us to build Web services that present the right level of information and interact with the right underlying business systems.

    Our business architecture team has been busy defining requirements for our next generation of e-commerce systems, and they have taken the next step to express these requirements in the form of a UML reference model. Figure 2 illustrates a portion of that model that is pertinent to our example component.


    Each class within this UML diagram represents a coarse-grained reference component that supports one or more interfaces. If we look into the Currency Exchange System component in more detail, we see that its two interfaces define a series of operations as shown in Figure 3.


    The operations defined here can be mapped against the methods defined by our EJB (see Table 1).


    Notice that some of our reference component methods are not directly supported by our EJB, and also that some of the capabilities of our EJB (e.g., our ability to configure conversion strategies) aren't reflected in our reference model. However, our mapping does show that we have a strong affinity between our desired business capabilities and this existing SDA.

    As our development team is tasked to build out portions of our next-generation business architecture, they will take advantage of our previously built business reference model to search for candidate SDAs that can help them do their work more efficiently. Let's assume that our team has the responsibility to build out a Web service supporting currency conversion. Their work activities flow as follows:
    1.   They begin their work by identifying the portion of the business reference model that applies to their project - specifically, the Currency Exchange System.
    2.   They then investigate the services and operations defined by that reference component.
    3.   For the set of selected operations, they initiate a search against the underlying SDAs mapped against the reference model. In this case, they discover our CurrencyExchange EJB.
    4.   The team then retrieves various artifacts as part of their evaluation process, ultimately concluding that they can take advantage of this asset in their Web services development project.

    How will they investigate the components and services associated with this model? While some groups have built reference models to asset mappings through spreadsheets and other similar tools, an SDA mapping and discovery engine can speed and improve this process dramatically.

    Depending upon the area of the model being investigated, our team might find multiple assets that support a set of business capabilities, at which point they need to determine if they should select one of these assets for future development or if they need to provide an encapsulation service that binds all of the existing assets together and ensures consistent data and behavior across them (if, for example, multiple customer information systems must be supported because of business merger activity in the past). Or they might discover that no existing assets support a portion of our model, indicating that "green-field" development is needed to support some expanded business capabilities. Regardless of the outcome, our team has a better view of what is available to them to use in the next stage of the process.

    The employ stage is where all of today's "whiz-bang" Web services tooling comes into play. With our Currency Exchange example, we will likely retrieve our EJB .jar file from its repository location and deposit it into a project within our IDE of choice, then use that IDE's Web service-generation capabilities to convert our SessionBean interface into a Web service with an associated WSDL file, Java client proxy, and other artifacts.

    As part of the employ phase, we have some decisions to make:

  • How should we expose the information from our specialized date range exception to our Web service client?
  • Do we choose to expose our conversion strategy capability on the Web service?
  • Do we create separate Web services for our currency conversion operations from our currency maintenance operations, or do we combine them into one service?

    Ultimately, as these newly built Web services are created and deployed, our team will complete the life cycle by feeding them back into their catalog, mapped against the business roadmap for which they were built. These Web services now become part of the developer's everyday toolkit - resulting in faster, higher quality, less expensive application development and integration.

    Taking the time to put our Web services and the underlying SDAs that already exist in our infrastructure into an IT library will ensure that the services we produce will provide true value to the business and not introduce more technology for technology's sake.


  • Schmelzer, R., and Bloomberg, J. ZapFlash, "Understanding the Real Costs of Integration": www.zapthink.com/flashes/10232002Flash.html
  • Alur, Crupi, and Malks. (2001) Core J2EE Patterns; Best Practices and Design Strategies, p. 261. (Prentice Hall PTR).
  • Gamma, Helm, Johnson, and Vlissides. (1994) Design Patterns: Elements of Object-Oriented Software, p. 315. Addison-Wesley.
  • More Stories By Brent Carlson

    Brent Carlson is vice president of technology and cofounder of LogicLibrary, a provider of software development asset (SDA) management tools. He is the coauthor of two books: San Francisco Design Patterns: Blueprints for Business Software (with James Carey and Tim Graser) and Framework Process Patterns: Lessons Learned Developing Application Frameworks (with James Carey). He also holds 16 software patents, with eight more currently under evaluation.

    Comments (0)

    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.

    @MicroservicesExpo Stories
    In his session at @DevOpsSummit at 20th Cloud Expo, Kelly Looney, director of DevOps consulting for Skytap, showed how an incremental approach to introducing containers into complex, distributed applications results in modernization with less risk and more reward. He also shared the story of how Skytap used Docker to get out of the business of managing infrastructure, and into the business of delivering innovation and business value. Attendees learned how up-front planning allows for a clean sep...
    In IT, we sometimes coin terms for things before we know exactly what they are and how they’ll be used. The resulting terms may capture a common set of aspirations and goals – as “cloud” did broadly for on-demand, self-service, and flexible computing. But such a term can also lump together diverse and even competing practices, technologies, and priorities to the point where important distinctions are glossed over and lost.
    Enterprise architects are increasingly adopting multi-cloud strategies as they seek to utilize existing data center assets, leverage the advantages of cloud computing and avoid cloud vendor lock-in. This requires a globally aware traffic management strategy that can monitor infrastructure health across data centers and end-user experience globally, while responding to control changes and system specification at the speed of today’s DevOps teams. In his session at 20th Cloud Expo, Josh Gray, Chie...
    "At the keynote this morning we spoke about the value proposition of Nutanix, of having a DevOps culture and a mindset, and the business outcomes of achieving agility and scale, which everybody here is trying to accomplish," noted Mark Lavi, DevOps Solution Architect at Nutanix, in this SYS-CON.tv interview at @DevOpsSummit at 20th Cloud Expo, held June 6-8, 2017, at the Javits Center in New York City, NY.
    We have already established the importance of APIs in today’s digital world (read about it here). With APIs playing such an important role in keeping us connected, it’s necessary to maintain the API’s performance as well as availability. There are multiple aspects to consider when monitoring APIs, from integration to performance issues, therefore a general monitoring strategy that only accounts for up-time is not ideal.
    In his session at 20th Cloud Expo, Mike Johnston, an infrastructure engineer at Supergiant.io, discussed how to use Kubernetes to set up a SaaS infrastructure for your business. Mike Johnston is an infrastructure engineer at Supergiant.io with over 12 years of experience designing, deploying, and maintaining server and workstation infrastructure at all scales. He has experience with brick and mortar data centers as well as cloud providers like Digital Ocean, Amazon Web Services, and Rackspace. H...
    When you focus on a journey from up-close, you look at your own technical and cultural history and how you changed it for the benefit of the customer. This was our starting point: too many integration issues, 13 SWP days and very long cycles. It was evident that in this fast-paced industry we could no longer afford this reality. We needed something that would take us beyond reducing the development lifecycles, CI and Agile methodologies. We made a fundamental difference, even changed our culture...
    As many know, the first generation of Cloud Management Platform (CMP) solutions were designed for managing virtual infrastructure (IaaS) and traditional applications. But that’s no longer enough to satisfy evolving and complex business requirements. In his session at 21st Cloud Expo, Scott Davis, Embotics CTO, will explore how next-generation CMPs ensure organizations can manage cloud-native and microservice-based application architectures, while also facilitating agile DevOps methodology. He wi...
    Docker is sweeping across startups and enterprises alike, changing the way we build and ship applications. It's the most prominent and widely known software container platform, and it's particularly useful for eliminating common challenges when collaborating on code (like the "it works on my machine" phenomenon that most devs know all too well). With Docker, you can run and manage apps side-by-side - in isolated containers - resulting in better compute density. It's something that many developer...
    These days, change is the only constant. In order to adapt and thrive in an ever-advancing and sometimes chaotic workforce, companies must leverage intelligent tools to streamline operations. While we're only at the dawn of machine intelligence, using a workflow manager will benefit your company in both the short and long term. Think: reduced errors, improved efficiency and more empowered employees-and that's just the start. Here are five other reasons workflow automation is leading a revolution...
    We have Continuous Integration and we have Continuous Deployment, but what’s continuous across all of what we do is people. Even when tasks are automated, someone wrote the automation. So, Jayne Groll evangelizes about Continuous Everyone. Jayne is the CEO of the DevOps Institute and the author of Agile Service Management Guide. She talked about Continuous Everyone at the 2016 All Day DevOps conference. She describes it as "about people, culture, and collaboration mapped into your value streams....
    Cloud adoption is often driven by a desire to increase efficiency, boost agility and save money. All too often, however, the reality involves unpredictable cost spikes and lack of oversight due to resource limitations. In his session at 20th Cloud Expo, Joe Kinsella, CTO and Founder of CloudHealth Technologies, tackled the question: “How do you build a fully optimized cloud?” He will examine: Why TCO is critical to achieving cloud success – and why attendees should be thinking holistically ab...
    Docker is on a roll. In the last few years, this container management service has become immensely popular in development, especially given the great fit with agile-based projects and continuous delivery. In this article, I want to take a brief look at how you can use Docker to accelerate and streamline the software development lifecycle (SDLC) process.
    We define Hybrid IT as a management approach in which organizations create a workload-centric and value-driven integrated technology stack that may include legacy infrastructure, web-scale architectures, private cloud implementations along with public cloud platforms ranging from Infrastructure-as-a-Service to Software-as-a-Service.
    Did you know that you can develop for mainframes in Java? Or that the testing and deployment can be automated across mobile to mainframe? In his session and demo at @DevOpsSummit at 21st Cloud Expo, Dana Boudreau, a Senior Director at CA Technologies, will discuss how increasingly teams are developing with agile methodologies, using modern development environments, and automating testing and deployments, mobile to mainframe.
    As DevOps methodologies expand their reach across the enterprise, organizations face the daunting challenge of adapting related cloud strategies to ensure optimal alignment, from managing complexity to ensuring proper governance. How can culture, automation, legacy apps and even budget be reexamined to enable this ongoing shift within the modern software factory?
    While some vendors scramble to create and sell you a fancy solution for monitoring your spanking new Amazon Lambdas, hear how you can do it on the cheap using just built-in Java APIs yourself. By exploiting a little-known fact that Lambdas aren’t exactly single-threaded, you can effectively identify hot spots in your serverless code. In his session at @DevOpsSummit at 21st Cloud Expo, Dave Martin, Product owner at CA Technologies, will give a live demonstration and code walkthrough, showing how ...
    There are several reasons why businesses migrate their operations to the cloud. Scalability and price are among the most important factors determining this transition. Unlike legacy systems, cloud based businesses can scale on demand. The database and applications in the cloud are not rendered simply from one server located in your headquarters, but is instead distributed across several servers across the world. Such CDNs also bring about greater control in times of uncertainty. A database hack ...
    @DevOpsSummit at Cloud Expo taking place Oct 31 - Nov 2, 2017, at the Santa Clara Convention Center, Santa Clara, CA, is co-located with the 21st International Cloud Expo and will feature technical sessions from a rock star conference faculty and the leading industry players in the world. The widespread success of cloud computing is driving the DevOps revolution in enterprise IT. Now as never before, development teams must communicate and collaborate in a dynamic, 24/7/365 environment. There is ...
    API Security is complex! Vendors like Forum Systems, IBM, CA and Axway have invested almost 2 decades of engineering effort and significant capital in building API Security stacks to lockdown APIs. The API Security stack diagram shown below is a building block for rapidly locking down APIs. The four fundamental pillars of API Security - SSL, Identity, Content Validation and deployment architecture - are discussed in detail below.