Welcome!

Microservices Expo Authors: Liz McMillan, Elizabeth White, Pat Romanski, Derek Weeks, LeanTaaS Blog

Related Topics: Microservices Expo

Microservices Expo: Article

The Tools Landscape

The Tools Landscape

Web services products have matured rapidly over the past 12 months, to the point where it's become acceptable to utilize the technology in major projects. However, though improving, the currently available toolkits can't be considered complete. This article surveys the rapidly evolving development tools landscape and addresses what tools a fully featured environment should provide to the Web-services developer.

IDE Integration
Historically, developers have toiled with an array of utilities, editors, and command-line tools. The ability to effectively navigate this maze of programs is a source of pride to many of them; however, this maze introduces a steep learning curve and, in the long run, lowers productivity. Some of the costs associated with such a nonintegrated approach are time lost switching back and forth between programs, time required to learn a new user interface, and cost of owning and managing multiple applications. It's also been costly for the tools vendors; each has written many thousands of lines of code that could have been shared between implementations. This includes code for the user interface, file and project management, version control, and many other housekeeping tasks.

The past year has seen major changes in the development landscape. Proprietary environments have fast lost ground to the concept of a single development framework into which additional tools can be deployed via a plug-in architecture. Products like JBuilder and NetBeans have provided this type of framework for some time, but it's fair to say that an industry-wide paradigm shift has coincided with the arrival of two über-frameworks: Microsoft's Visual Studio .NET and the open-source Eclipse project.

IBM's reasons for donating Eclipse to the open-source community are no mystery. If the non-Microsoft community doesn't close ranks around a single framework, it will not be economically feasible to compete with the de facto IDE monopoly for Windows development: Visual Studio. Developing an IDE is an expensive business - IBM spent $40 million on Eclipse. This may seem a costly bit of software to give away, but having the developer community adopt its technology gives IBM a significant head start since IBM's tools already run in Eclipse, while other vendors must go to considerable lengths to move to a plug-in architecture. Tools vendors may not wish to swallow this bait, but the drive toward a single IDE platform is given unassailable momentum by two converging forces: the developer-side desire for an integrated experience, and the economics of proprietary development.

One of the consequences of IDE integration is that products built on the same framework will largely look the same. The mainstream toolsets will also have significant overlap in functionality, though vendors will try hard to differentiate their offerings. This commoditization of the tools market is bad news for smaller vendors. In a battle of commodities, the larger, better-resourced players tend to win. It's not all gloom though. As vendors strive to outshine the competition, we can expect to see higher quality and more innovative software. Another plus: open-source groups and creators of niche or boutique software can take advantage of the IDE frameworks to deliver their software in a first-rate package. Although developers will initially lose some choice due to the inevitable process of consolidation in the tools market, this will be more than offset by improved product sets from surviving vendors and a more diverse range of software from smaller software houses. Web-services developers in particular stand to gain, as there are a great number of companies targeting this space.

Basic Tools
Before we survey some of the more interesting tools that are becoming available, let's establish the basic functionality required to develop Web services. From within the IDE, the developer should be able to:

  • Generate Web Services Description Language (WSDL) from a component: This should be as simple as right-clicking com. acme.MyClass and selecting "Generate WSDL...". This command should bring up a dialog that allows the developer to specify which methods to expose, what to name the Web service, and other basic options.
  • Generate stubs and skeletons from WSDL: It should be possible to generate both client-side stubs and server-side skeletons, preferably in a variety of languages. For Java, the developer should have the option of generating EJB or regular Java skeletons.
  • Deploy a Web service: Deployment can be an intricate process, so the IDE should provide a wizard to help assemble the classes, documents, and configuration data necessary to successfully deploy. Several products have introduced the concept of a Web Services Archive, similar to a JAR or WAR file. This can make it considerably easier to manage deployment, especially across multiple machines.

    Note that the degree to which an IDE exposes WSDL can vary. In Visual Studio, the developer adds WSDL to a project by invoking the "Add Web Reference..." command. This automatically generates client proxy code and adds it to the project. The WSDL is effectively hidden from the developer. Hiding the complexity of WSDL is fine if your application is a consumer of Web services, but server-side development requires more control. This is particularly the case with Java because Web services haven't been tightly integrated into the JVM as Microsoft has done with the .NET Common Language Runtime (CLR). We might expect the toolset to grant the developer considerable control over the WSDL. In particular, it's important to be able to customize the mapping between WSDL and the native language.

    WSDL Mapping
    When WSDL is generated, the created schema types are typically named after classes, with elements named after the members of the class. Frequently, the developer wants to rename or omit a member, or otherwise change how the class is serialized. Why? Perhaps the Web service has to conform to a specific WSDL interface defined by a standards organization or commercial partner. Or it might be for more cosmetic reasons, such as changing unhelpful element names; or for business reasons, such as not exposing sensitive information.

    To serialize an object, a Web services platform uses a mapping layer that defines how the native representation (e.g., a Java class) is mapped to XML (see Figure 1). The method and degree of control over this layer varies by product, but there are three common ways to provide customization:

     

  • Configuration file: This will usually allow fairly limited customization, such as changing member names or omitting elements.
  • XSLT: The native object is first serialized per the default rules, and then an XSLT transform is performed, allowing a greater control. However, developers can find XSLT difficult to work with, and the transform is processor intensive.
  • Custom serialization class: Instead of using reflection to inspect and serialize the object, the serialization process can be delegated to a helper class created by the developer. This mechanism provides almost unlimited control, although modifying and managing the additional classes is cumbersome.

    Most platforms support the use of at least one method of directly editing the mapping layer. However, tools support is still weak. In the near future, developers can expect to see software that provides full round-trip support for editing WSDL. Such an editor will allow developers to modify elements in the WSDL and will automatically propagate these changes to the mapping layer. Note that it should be possible to perform the converse operation: modify the source component, and the changes are propagated toward the WSDL. Mapping is one concept that developers will encounter frequently with Web services. This is because of an under-appreciated enabling technology: XSLT.

    XSLT and Graphical Mapping
    XSLT is a technology that most developers haven't had significant contact with. It's often thought of in the context of generating HTML pages, but its utility extends far beyond that. As mentioned earlier, XSLT can be used to control the mapping between WSDL and a native language. Some other uses are:

    • Map requests from an older version of a Web service into the new version's format
    • Map non-SOAP XML documents into SOAP requests
    XSLT has a steep learning curve - for many developers the "side effect-free" programming model is less than intuitive to grasp, so good tools are essential. Thankfully XSLT lends itself quite well to graphical editing, where two schemas are laid out side by side and related elements are linked by dragging one to the other (see Figure 2).

     

    Let's look at an example. AirportWeather is a publicly available Web service that reports on conditions at airport weather stations around the world. There's also a recently created successor Web service, GlobalWeather, which is faster and has a richer data model. Both of the services have an operation that takes one parameter, the weather station code (e.g., JFK or SFO), and returns a weather report for that location.

    We can use XSLT to transform a SOAP request for AirportWeather into a SOAP request for GlobalWeather. Instead of creating the XSLT by hand, we load the source schema (AirportWeather.wsdl) and the target schema (GlobalWeather.wsdl) side by side. Then we graphically link the two parameters - AirportWeather's nonintuitively named "arg0" and GlobalWeather's "code" - and the mapper will generate the necessary XSLT. In a similar manner, we can use XSLT to transform a non-SOAP XML document into a GlobalWeather request (see Figure 3).

     

    XSLT is an underused technology with great potential, in particular for integrating Web services and legacy XML applications. A good development environment will support the graphical creation of XSLT, and it should allow the easy deployment of XSLT documents into your Web-services platform.

    Testing
    Once a Web service is built and deployed, the next step is to test it. Testing can range from merely verifying that a service is operational to a full automated test suite. The most common testing approach is to generate a client proxy from the WSDL and write a test class to invoke the proxy. But there's a better way: the IDE can generate a test class which invokes the Web service's operations using default parameter values. For Java, the test cases can make use of the JUnit test framework and the Ant build system to make it easy to integrate Web service testing into existing automated test suites.

    Another approach is to generate a SOAP document from the schema information in the WSDL and send it directly to the Web service endpoint using HTTP. This isn't amenable to automated testing but is useful if the developer is interested in the lower-level details of the SOAP messages. However, the friendliest approach is to generate an HTML Web client that's deployed on the Web server alongside the Web service. This Web client is typically based on JSP or ASP and consists of one page for each operation. The form fields correspond to the operation parameters, and submission of the form results in the Web service being invoked. As well as being a fast means of verifying that a service is alive, this is also an effective way of demonstrating a developing Web service.

    Debugging
    Debugging a Web service is essentially the same as debugging any other server-side software, such as an EJB. The IDE's debugger attaches to the service process using the standard mechanisms for the platform, which usually involves starting the server in debug mode. But unlike an EJB, the raw messages between a client and a Web service are intelligible and of interest to the developer.

    There are two quite similar ways of monitoring SOAP messages. A TCP tunnel is a program that listens on a port and directs all traffic to a specified host and port (e.g., tunnel from localhost:7000 to server.acme. com: 8000). The tunnel program can then display the messages in a GUI. To enable tunneling, the SOAP endpoint URL used by the client must be modified to point at the tunnel's listening port.

    Like a TCP tunnel, an HTTP proxy listens on a port, but it has specific knowledge of the HTTP protocol. The proxy reads the "Host" field in the HTTP header and directs traffic to the indicated location. A proxy is more transparent than a tunnel in that proxy settings can generally be set on a process-wide basis and thus modification of individual endpoints is not required.

    Conclusion
    Monitoring tools were an indispensable item in the early days of Web services, when developers spent a lot of time working with raw SOAP messages. Although a development environment should still provide the ability to work at this level, many developers will never need to do so. It's a sign of the maturity of the technology that this is the case. Web services tools are entering the mainstream.

  • More Stories By Neil O'Toole

    Neil O'Toole is a Technology Evangelist at Cape Clear, where he is responsible for promoting the adoption and effective use of Web Services by developers. He manages the CapeScience developer network (www.capescience.com), moderates the Cape Clear newsgroup, and works with the Web Services development community to help define Cape Clear
    product direction.
    He is the author of the popular NetTool debugging utility, has written dozens of technical articles and papers, and is an accomplished public speaker.
    Before beginning his career in evangelism, Neil was a senior developer at Cape Clear. Prior to that he worked with Goldman Sachs (an investment bank), CR2 (banking software), and Esat Net, part of British Telecom. He holds a first class degree in Computer Science from Trinity College Dublin.

    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
    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, explored how next-generation CMPs ensure organizations can manage cloud-native and microservice-based application architectures, while also facilitating agile DevOps methodology. He expla...
    DevOps promotes continuous improvement through a culture of collaboration. But in real terms, how do you: Integrate activities across diverse teams and services? Make objective decisions with system-wide visibility? Use feedback loops to enable learning and improvement? With technology insights and real-world examples, in his general session at @DevOpsSummit, at 21st Cloud Expo, Andi Mann, Chief Technology Advocate at Splunk, explored how leading organizations use data-driven DevOps to close th...
    "WineSOFT is a software company making proxy server software, which is widely used in the telecommunication industry or the content delivery networks or e-commerce," explained Jonathan Ahn, COO of WineSOFT, 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.
    Some people are directors, managers, and administrators. Others are disrupters. Eddie Webb (@edwardawebb) is an IT Disrupter for Software Development Platforms at Liberty Mutual and was a presenter at the 2016 All Day DevOps conference. His talk, Organically DevOps: Building Quality and Security into the Software Supply Chain at Liberty Mutual, looked at Liberty Mutual's transformation to Continuous Integration, Continuous Delivery, and DevOps. For a large, heavily regulated industry, this task ...
    The notion of improving operational efficiency is conspicuously absent from the healthcare debate - neither Obamacare nor the newly proposed GOP plan discusses the impact that a step-function improvement in efficiency could have on access to healthcare (through more capacity), quality of healthcare services (through reduced wait times for patients) or cost (through better utilization of scarce, expensive assets).
    SYS-CON Events announced today that Synametrics Technologies will exhibit at SYS-CON's 22nd International Cloud Expo®, which will take place on June 5-7, 2018, at the Javits Center in New York, NY. Synametrics Technologies is a privately held company based in Plainsboro, New Jersey that has been providing solutions for the developer community since 1997. Based on the success of its initial product offerings such as WinSQL, Xeams, SynaMan and Syncrify, Synametrics continues to create and hone inn...
    The past few years have seen a huge increase in the amount of critical IT services that companies outsource to SaaS/IaaS/PaaS providers, be it security, storage, monitoring, or operations. Of course, along with any outsourcing to a service provider comes a Service Level Agreement (SLA) to ensure that the vendor is held financially responsible for any lapses in their service which affect the customer’s end users, and ultimately, their bottom line. SLAs can be very tricky to manage for a number ...
    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...
    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...
    The past few years have brought a sea change in the way applications are architected, developed, and consumed—increasing both the complexity of testing and the business impact of software failures. How can software testing professionals keep pace with modern application delivery, given the trends that impact both architectures (cloud, microservices, and APIs) and processes (DevOps, agile, and continuous delivery)? This is where continuous testing comes in. D
    In a recent post, titled “10 Surprising Facts About Cloud Computing and What It Really Is”, Zac Johnson highlighted some interesting facts about cloud computing in the SMB marketplace: Cloud Computing is up to 40 times more cost-effective for an SMB, compared to running its own IT system. 94% of SMBs have experienced security benefits in the cloud that they didn’t have with their on-premises service
    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,...
    Admiral Calcote - also known as Lee Calcote (@lcalcote) or the Ginger Geek to his friends - gave a presentation entitled Characterizing and Contrasting Container Orchestrators at the 2016 All Day DevOps conference. Okay, he isn't really an admiral - nor does anyone call him that - but he used the title admiral to describe what container orchestrators do, relating it to an admiral directing a fleet of container ships. You could also say that they are like the conductor of an orchestra, directing...
    Our work, both with clients and with tools, has lead us to wonder how it is that organizations are handling compliance issues in the cloud. The big cloud vendors offer compliance for their infrastructure, but the shared responsibility model requires that you take certain steps to meet compliance requirements. Which lead us to start poking around a little more. We wanted to get a picture of what was available, and how it was being used. There is a lot of fluidity in this space, as in all things c...
    The goal of Microservices is to improve software delivery speed and increase system safety as scale increases. Microservices being modular these are faster to change and enables an evolutionary architecture where systems can change, as the business needs change. Microservices can scale elastically and by being service oriented can enable APIs natively. Microservices also reduce implementation and release cycle time and enables continuous delivery. This paper provides a logical overview of the Mi...
    Gaining visibility in today’s sprawling cloud infrastructure is complex and laborious, involving drilling down into tools offered by various cloud services providers. Enterprise IT organizations need smarter and effective tools at their disposal in order to address this pertinent problem. Gaining a 360 - degree view of the cloud costs requires collection and analysis of the cost data across all cloud infrastructures used inside an enterprise.
    "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.
    "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.
    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...
    The “Digital Era” is forcing us to engage with new methods to build, operate and maintain applications. This transformation also implies an evolution to more and more intelligent applications to better engage with the customers, while creating significant market differentiators. In both cases, the cloud has become a key enabler to embrace this digital revolution. So, moving to the cloud is no longer the question; the new questions are HOW and WHEN. To make this equation even more complex, most ...