Microservices Expo Authors: Pat Romanski, Dalibor Siroky, Stackify Blog, Elizabeth White, Liz McMillan

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
    While some developers care passionately about how data centers and clouds are architected, for most, it is only the end result that matters. To the majority of companies, technology exists to solve a business problem, and only delivers value when it is solving that problem. 2017 brings the mainstream adoption of containers for production workloads. In his session at 21st Cloud Expo, Ben McCormack, VP of Operations at Evernote, discussed how data centers of the future will be managed, how the p...
    The nature of test environments is inherently temporary—you set up an environment, run through an automated test suite, and then tear down the environment. If you can reduce the cycle time for this process down to hours or minutes, then you may be able to cut your test environment budgets considerably. The impact of cloud adoption on test environments is a valuable advancement in both cost savings and agility. The on-demand model takes advantage of public cloud APIs requiring only payment for t...
    It has never been a better time to be a developer! Thanks to cloud computing, deploying our applications is much easier than it used to be. How we deploy our apps continues to evolve thanks to cloud hosting, Platform-as-a-Service (PaaS), and now Function-as-a-Service. FaaS is the concept of serverless computing via serverless architectures. Software developers can leverage this to deploy an individual "function", action, or piece of business logic. They are expected to start within milliseconds...
    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? In her Day 2 Keynote at @DevOpsSummit at 21st Cloud Expo, Aruna Ravichandran, VP, DevOps Solutions Marketing, CA Technologies, was jo...
    You know you need the cloud, but you’re hesitant to simply dump everything at Amazon since you know that not all workloads are suitable for cloud. You know that you want the kind of ease of use and scalability that you get with public cloud, but your applications are architected in a way that makes the public cloud a non-starter. You’re looking at private cloud solutions based on hyperconverged infrastructure, but you’re concerned with the limits inherent in those technologies.
    Is advanced scheduling in Kubernetes achievable?Yes, however, how do you properly accommodate every real-life scenario that a Kubernetes user might encounter? How do you leverage advanced scheduling techniques to shape and describe each scenario in easy-to-use rules and configurations? In his session at @DevOpsSummit at 21st Cloud Expo, Oleg Chunikhin, CTO at Kublr, answered these questions and demonstrated techniques for implementing advanced scheduling. For example, using spot instances and co...
    The cloud era has reached the stage where it is no longer a question of whether a company should migrate, but when. Enterprises have embraced the outsourcing of where their various applications are stored and who manages them, saving significant investment along the way. Plus, the cloud has become a defining competitive edge. Companies that fail to successfully adapt risk failure. The media, of course, continues to extol the virtues of the cloud, including how easy it is to get there. Migrating...
    For DevOps teams, the concepts behind service-oriented architecture (SOA) are nothing new. A style of software design initially made popular in the 1990s, SOA was an alternative to a monolithic application; essentially a collection of coarse-grained components that communicated with each other. Communication would involve either simple data passing or two or more services coordinating some activity. SOA served as a valid approach to solving many architectural problems faced by businesses, as app...
    Some journey to cloud on a mission, others, a deadline. Change management is useful when migrating to public, private or hybrid cloud environments in either case. For most, stakeholder engagement peaks during the planning and post migration phases of a project. Legacy engagements are fairly direct: projects follow a linear progression of activities (the “waterfall” approach) – change managers and application coders work from the same functional and technical requirements. Enablement and develo...
    Gone are the days when application development was the daunting task of the highly skilled developers backed with strong IT skills, low code application development has democratized app development and empowered a new generation of citizen developers. There was a time when app development was in the domain of people with complex coding and technical skills. We called these people by various names like programmers, coders, techies, and they usually worked in a world oblivious of the everyday pri...
    From manual human effort the world is slowly paving its way to a new space where most process are getting replaced with tools and systems to improve efficiency and bring down operational costs. Automation is the next big thing and low code platforms are fueling it in a significant way. The Automation era is here. We are in the fast pace of replacing manual human efforts with machines and processes. In the world of Information Technology too, we are linking disparate systems, softwares and tool...
    DevOps is good for organizations. According to the soon to be released State of DevOps Report high-performing IT organizations are 2X more likely to exceed profitability, market share, and productivity goals. But how do they do it? How do they use DevOps to drive value and differentiate their companies? We recently sat down with Nicole Forsgren, CEO and Chief Scientist at DORA (DevOps Research and Assessment) and lead investigator for the State of DevOps Report, to discuss the role of measure...
    DevOps is under attack because developers don’t want to mess with infrastructure. They will happily own their code into production, but want to use platforms instead of raw automation. That’s changing the landscape that we understand as DevOps with both architecture concepts (CloudNative) and process redefinition (SRE). Rob Hirschfeld’s recent work in Kubernetes operations has led to the conclusion that containers and related platforms have changed the way we should be thinking about DevOps and...
    "As we've gone out into the public cloud we've seen that over time we may have lost a few things - we've lost control, we've given up cost to a certain extent, and then security, flexibility," explained Steve Conner, VP of Sales at Cloudistics,in this SYS-CON.tv interview at 20th Cloud Expo, held June 6-8, 2017, at the Javits Center in New York City, NY.
    These days, APIs have become an integral part of the digital transformation journey for all enterprises. Every digital innovation story is connected to APIs . But have you ever pondered over to know what are the source of these APIs? Let me explain - APIs sources can be varied, internal or external, solving different purposes, but mostly categorized into the following two categories. Data lakes is a term used to represent disconnected but relevant data that are used by various business units wit...
    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...
    "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.
    "Cloud4U builds software services that help people build DevOps platforms for cloud-based software and using our platform people can draw a picture of the system, network, software," explained Kihyeon Kim, CEO and Head of R&D at Cloud4U, 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.
    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 ...
    DevOps is often described as a combination of technology and culture. Without both, DevOps isn't complete. However, applying the culture to outdated technology is a recipe for disaster; as response times grow and connections between teams are delayed by technology, the culture will die. A Nutanix Enterprise Cloud has many benefits that provide the needed base for a true DevOps paradigm. In their Day 3 Keynote at 20th Cloud Expo, Chris Brown, a Solutions Marketing Manager at Nutanix, and Mark Lav...